Deletes a routing rule.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request headers

This operation uses only common request headers. For more information, see Common request parameters and common response parameters.

Request syntax

DELETE /pop/v1/sam/ingress/Ingress HTTP/1.1

Request parameters

Parameter Type Position Required Example Description
IngressId Long Query Yes 87

The ID of the routing rule that you want to delete. You can obtain the ID by calling the ListIngresses operation.

Response parameters

Parameter Type Example Description
RequestId String 91F93257-7A4A-4BD3-9A7E-2F6EAE6D****

The ID of the request.

Message String success

The returned message.

TraceId String 0a98a02315955564772843261e****

The ID of the trace. It is used to query the details of a request.

Data Object

The returned data.

IngressId Long 87

The ID of the routing rule that you want to delete.

ErrorCode String This parameter is left empty.

The error code.

  • The ErrorCode parameter is not returned when the request succeeds.
  • The ErrorCode parameter is returned when the request fails. For more information, see Error codes in this topic.
Code String 200

The HTTP status code. Valid values:

  • 2xx: indicates that the request was successful.
  • 3xx: indicates that the request was redirected.
  • 4xx: indicates that the request failed.
  • 5xx: indicates that a server error occurred.
Success Boolean true

Indicates whether the routing rule was deleted. Valid values:

  • true: indicates that the routing rule was deleted.
  • false: indicates that the routing rule could not be deleted.

Examples

Sample requests

DELETE /pop/v1/sam/ingress/Ingress?IngressId=87 HTTP/1.1
Host:sae.aliyuncs.com
Content-Type:application/json

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<DeleteIngressResponse>
    <RequestId>91F93257-7A4A-4BD3-9A7E-2F6EAE6D****</RequestId>
    <Message>success</Message>
    <TraceId>0a98a02315955564772843261e****</TraceId>
    <Data>
        <IngressId>87</IngressId>
    </Data>
    <Code>200</Code>
    <Success>true</Success>
</DeleteIngressResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "91F93257-7A4A-4BD3-9A7E-2F6EAE6D****",
  "Message" : "success",
  "TraceId" : "0a98a02315955564772843261e****",
  "Data" : {
    "IngressId" : 87
  },
  "Code" : "200",
  "Success" : true
}

Error codes

HttpCode Error code Error message Description
400 InvalidParameter.NotEmpty You must specify the parameter %s. The error message returned because the value of the %s parameter is invalid. This parameter cannot be left empty.
400 InvalidParameter.Obviously The specified parameter is invalid {%s}. The error message returned because the value of the %s parameter is invalid.
400 InvalidParameter.WithMessage The parameter is invalid {%s}: %s The error message returned because the value of the %s parameter is invalid: %s.
500 OperationFailed.RPCError Internal RPC request processing error. The error message returned because a Remote Procedure Call (RPC) request fails to be processed.

For a list of error codes, visit the API Error Center.