All Products
Search
Document Center

Virtual Private Cloud:DissociateRouteTablesFromVpcGatewayEndpoint

Last Updated:Aug 28, 2026

Disassociates a gateway endpoint from a route table.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

No authorization for this operation. If you encounter issues with this operation, contact technical support.

Request parameters

Parameter

Type

Required

Description

Example

EndpointId

string

Yes

The ID of the gateway endpoint to be disassociated from the route table.

vpce-bp11cwae3p6z7ftbm****

RouteTableIds

array

Yes

The ID of the route table. Valid values of N: 1 to 20. You can disassociate a gateway endpoint from up to 20 route tables at a time.

vtb-m5elgtm3aj586iitr****

string

No

The ID of the route table.

vtb-m5elgtm3aj586iitr****

ClientToken

string

No

The client token that ensures the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.

Note

If you do not specify this parameter, the system uses the request ID as the client token. The request ID may be different for each request.

TF-DissociateRouteTablesFromVpcGatewayEndpoint-1634369235-8f****

DryRun

boolean

No

Specifies whether to perform only a dry run, without sending the actual request. Valid values:

  • true: performs only a dry run. The system checks the request for potential issues, including missing parameter values, incorrect request syntax, and service limits. If the request fails the dry run, an error message is returned. If the request passes the dry run, the DryRunOperation error code is returned.

  • false (default): performs a dry run and sends the actual request. If the request passes the dry run, a 2xx HTTP status code is returned and the operation is performed.

false

RegionId

string

Yes

The region ID of the gateway endpoint.

You can call the DescribeRegions operation to query the most recent list of regions.

cn-hangzhou

Response elements

Element

Type

Description

Example

object

The returned information.

RequestId

string

The request ID.

30F711D5-E7E2-5D42-A247-0FA7288BEAAA

Examples

Success response

JSON format

{
  "RequestId": "30F711D5-E7E2-5D42-A247-0FA7288BEAAA"
}

Error codes

HTTP status code

Error code

Error message

Description

400 OperationFailed.ConcurrentOperation The operation is failed because of concurrent operation.
400 IdempotentParameterMismatch The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical.
400 ResourceNotFound.GatewayEndpoint The specified resource gateway endpoint is not found. The error message returned because the specified gateway endpoint does not exist.
400 IncorrectStatus.GatewayEndpoint The status of GatewayEndpoint [%s] is incorrect.
400 ResourceNotFound.RouteTable The specified resource routetable is not found.
400 IncorrectStatus.RouteTable The status of route table [%s] is incorrect.
400 ResourceNotFound.Association The specified resource gateway endpoint is not associated.
400 IncorrectStatus.RouteEntry Some route entry status blocked this operation.
400 Forbbiden User not authorized to operate on the specified resource.
400 InvalidRegionId.NotFound The regionId provided does not exist in our records. The RegionId parameter is set to an invalid value. Specify a valid value and try again.
400 IncorrectStatus.CenStatus The CenStatus of Vpc is incorrect.
400 ResourceNotFound.RouteEntry The specified resource is not found.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.