Docs

Transit Router

Route policy

AssociateTransitRouterRoutePolicyToRouteTable - Associating a route policy with a TR route table

Call the AssociateTransitRouterRoutePolicyToRouteTable API to associate the specified route policy to the specified Transit Router (TR) route table.

Debug

API Explorer

You can initiate calls online through API Explorer without paying attention to the signature generation process and quickly obtain the call results.

Go to debug

Request parameters

The following only details request parameters specific to this API and key common parameters. For more information, see Common parameters.

Action String required Example value: AssociateTransitRouterRoutePolicyToRouteTable

The interface name. The current API name is AssociateTransitRouterRoutePolicyToRouteTable.

Version String required Example: 2020-04-01

The interface version. The current API version is 2020-04-01.

TransitRouterRoutePolicyTableId String required Example value: tr-rpt-1i5i8khf9m58gae5kcx6****

The ID of the route policy. You can call the DescribeTransitRouterRoutePolicyTables API to obtain the ID of the route policy.

TransitRouterRouteTableId String required Example value: tr-rtb-13n2l4c****

ID of the TR route table. You can call the DescribeTransitRouterRouteTables API to obtain the TR route table ID.

Direction String required Example value: In

The direction of the route policy. Values:

In: Inbound. The direction that TR receives routes from a network instance only if they meet the route policy.

Out: Outbound. The direction that TR synchronizes routes to a network instance only if they meet the route policy.

Response parameters

This API does not have specific response parameters. For more information, see Response structure.

Request examples

GET /?Action=AssociateTransitRouterRoutePolicyToRouteTable&Version=2020-04-01&TransitRouterRoutePolicyTableId=tr-rpt-1i5i8khf9m58gae5kcx6****&TransitRouterRouteTableId=tr-rtb-13n2l4c****&Direction=In HTTP/1.1​
Host: transitrouter.cn-beijing.volcengineapi.com​
X-Date: 20250815T033756Z​
Authorization: HMAC-SHA256 Credential=Adfks******wekfwe/20250815/cn-beijing/transitrouter/request, SignedHeaders=host;x-date, Signature=47a7d934ff7b37c03938******cd7b8278a40a1057690c401e92246a0e41085f​

Response examples

{​
    "ResponseMetadata": {​
        "RequestId": "20250815113759180069021080F77CD8",​
        "Action": "AssociateTransitRouterRoutePolicyToRouteTable",​
        "Version": "2020-04-01",​
        "Service": "transitrouter",​
        "Region": "cn-beijing"​
    },​
    "Result": {}​
}​

Error codes

The table below describes the error codes for this API that are associated with business logic. For more information, see Common error codes.

Status code	Error codes	Error message	Explanation
400	InvalidRoutePolicy.DirectionInvalid	The specified Transit Router route policy direction is invalid, only In and Out are supported.	The specified route policy direction is invalid. Only In and Out are supported.
400	InvalidTransitRouter.InvalidBusinessStatus	The request is denied because the specified Transit Router is shut down due to arrears.	The specified Transit Router (TR) is suspended due to overdue payments. Action unsupported.
400	InvalidTransitRouter.InvalidStatus	The specified Transit Router is not in the correct status for the request.	The specified Transit Router (TR) is in a status that cannot respond to the request.
400	InvalidTransitRouterRoutePolicyAssociation.TransitRouterMismatch	The specified route table and route policy do not belong to one same Transit Router.	The specified route table does not belong to the TR associated with the route policy.
403	Forbidden.NoPermissionToOperate	You are not authorized to operate the specified resource.	No permission to manage the specified resource.
404	InvalidTransitRouterRoutePolicy.NotFound	The specified Transit Router route policy does not exist.	The specified route policy does not exist.
404	InvalidTransitRouterRouteTable.NotFound	The specified route table does not exist.	The specified Transit Router (TR) route table does not exist.
409	InvalidTransitRouterRoutePolicyAssociation.Conflict	The specified Transit Router route table has already been associated with a route policy.	The route policy is associated with the specified route table. Duplicate configuration is not permitted.
409	InvalidTransitRouterRoutePolicyAssociation.DirectionConflict	The specified direction conflicts with the direction of the Transit Router route policy.	The specified direction conflicts with the direction of the route policy.

Last updated: 2025.12.29 19:24:05