vpc — Virtual Private Cloud
vpc · 2017-03-12

DeleteRoutes

POST

Delete routing policies in batches from a route table.

Wire call

Converge Cloud is RPC over HTTP. There is one path — / — and the action travels in the X-TC-Action header. The /vpc/DeleteRoutes path used in the OpenAPI document is a documentation convenience so each action is addressable; it is not a route on the server.

curl
curl -sS https://vpc.api3.convergecloud.com/ \
  -H 'Authorization: TC3-HMAC-SHA256 Credential=<SecretId>/<YYYY-MM-DD>/vpc/tc3_request, SignedHeaders=content-type;host;x-tc-action, Signature=<sig>' \
  -H 'Content-Type: application/json; charset=utf-8' \
  -H 'Host: vpc.api3.convergecloud.com' \
  -H 'X-TC-Action: DeleteRoutes' \
  -H 'X-TC-Version: 2017-03-12' \
  -H 'X-TC-Timestamp: <unix-seconds>' \
  -H 'X-TC-Region: luzon' \
  -d '{"RouteTableId":"<RouteTableId>","Routes":"<Routes>"}'

Request parameters

FieldTypeRequiredDescription
RouteTableIdstringYesRoute table instance ID.
RoutesRoute[]YesRouting policy object. Only the `RouteId` field is required when deleting a routing policy.

Response

Fields are returned inside the Response envelope. Converge Cloud answers HTTP 200 for errors as well as successes, so read Response.Error rather than the status code — and test for the presence of that object, because Code is occasionally the empty string.

FieldTypeDescription
RouteSetRoute[]Details of the routing policy that has been deleted.
RequestIdstringThe unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.
Success
{
  "Response": {
    "RouteSet": …,
    "RequestId": "…"
  }
}
Error
{
  "Response": {
    "Error": { "Code": "…", "Message": "…" },
    "RequestId": "…"
  }
}

Try it

CredentialThe key never leaves this tab — it signs the request here. The signed request goes to /api-relay/vpc.
Request bodyvalid JSONPOST vpc.api3.convergecloud.com · DeleteRoutes
Recorded example response — captured 2026-09-17
{
  "Response": {
    "RouteSet": [
      {
        "RouteTableId": "rtb-90dtbn2g",
        "RouteId": 1086,
        "RouteItemId": "rti-9zgml95n",
        "DestinationCidrBlock": "0.0.0.0/0",
        "GatewayType": "NAT",
        "GatewayId": "nat-b6ku8fsk",
        "RouteDescription": "example default via nat",
        "CreatedTime": "2026-09-17 10:22:58"
      }
    ],
    "RequestId": "f69d4344-6498-faf1-acd2-54bebe1d4d7c"
  }
}

What failure looks like

Example error responses for this action. Match on Code.

Recorded error 1
{
  "Response": {
    "Error": {
      "Code": "ResourceNotFound",
      "Message": "指定资源 `rtb-00000000` 未找到。"
    },
    "RequestId": "a8f715ae-2105-302e-43e4-652c01a60dbd"
  }
}
Recorded error 2
{
  "Response": {
    "Error": {
      "Code": "ResourceNotFound",
      "Message": "指定资源 `rtb-00000000` 未找到。"
    },
    "RequestId": "768e4e94-2f79-ef03-6d79-70790628407d"
  }
}

Behaviour

Identifies routes by RouteItemId, not by the numeric RouteId.