Delete a gateway
delete
/apiplatform/management/v1/gateways/{gwId}
Deletes the {gwId}
gateway.
You can't delete a logical gateway if nodes are registered or requesting registration to it. Ensure you unregister all nodes from it and that you have the proper permission before trying again.
Users requesting this resource must be assigned Gateway Manager role and must be issued the Manage Gateway grant for the specified gateway.
Request
Supported Media Types
- application/json
Path Parameters
-
gwId: string
A unique ID referencing a specific gateway.
Response
Supported Media Types
- application/json
204 Response
The gateway was deleted.
403 Response
Forbidden.
Root Schema : Error
Type:
Show Source
object
-
detail(optional):
string
Detailed error message
-
errorCode(optional):
string
Application specific error code
-
errorDetails(optional):
array errorDetails
additional errors
-
errorPath(optional):
string
-
instance(optional):
string
URI to the link that provides more detail about the error
-
status(optional):
string
HTTP status code
-
title:
string
Summary error message
-
type:
string
Error type
500 Response
Unexpected error.
Root Schema : Error
Type:
Show Source
object
-
detail(optional):
string
Detailed error message
-
errorCode(optional):
string
Application specific error code
-
errorDetails(optional):
array errorDetails
additional errors
-
errorPath(optional):
string
-
instance(optional):
string
URI to the link that provides more detail about the error
-
status(optional):
string
HTTP status code
-
title:
string
Summary error message
-
type:
string
Error type
Examples
The following example shows how to delete a gateway by submitting a DELETE request on the REST resource using cURL. For more information about cURL, see Use cURL
curl -i -X DELETE
-H "Authorization: Bearer access_token"
https://example.com/apiplatform/management/v1/gateways/{gwId}
{gwId}
is the unique Id of a specific gateway. To retrieve available gateway Ids, see Get gateways
Example of Response Headers
The following shows an example of the response headers.
HTTP /1.1 204 No Content Server: Oracle-Traffic-Director/12.2.1.0.0 Date: Thu, 16 Mar 2017 09:28:21 GMT X-oracle-dms-ecid: f102c33f-1c5b-4409-806d-03bf5706c492-00026e33 X-oracle-dms-rid: 0:1 Via: 1.1 otd_opc Proxy-agent: Oracle-Traffic-Director/12.2.1.0.0