Help Center/ Enterprise Router/ API Reference/ APIs/ Propagations/ Creating a Route Propagation
Updated on 2026-03-20 GMT+08:00

Creating a Route Propagation

Function

This API is used to create a route propagation. A propagation can be created for each attachment to propagate routes to one or more route tables on an enterprise router.

Calling Method

For details, see Calling APIs.

Authorization Information

Each account root user has all the permissions required to call all APIs, but IAM users must be assigned the following required identity policy-based permissions. For details about the required permissions, see Permissions Policies and Supported Actions.

Action

Access Level

Resource Type (*: required)

Condition Key

Alias

Dependencies

er:routeTables:enablePropagation

Write

routeTables *

  • g:EnterpriseProjectId

  • g:ResourceTag/<tag-key>

er:propagations:enable

-

attachments *

  • g:EnterpriseProjectId

  • g:ResourceTag/<tag-key>

URI

POST /v3/{project_id}/enterprise-router/{er_id}/route-tables/{route_table_id}/enable-propagations

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID

er_id

Yes

String

Enterprise router ID

route_table_id

Yes

String

Route table ID

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

X-Client-Token

No

String

Idempotence identifier

Minimum: 1

Maximum: 64

Table 3 Request body parameters

Parameter

Mandatory

Type

Description

attachment_id

No

String

Unique ID of the attachment

Response Parameters

Status code: 202

Table 4 Response header parameters

Parameter

Type

Description

X-Client-Token

String

Idempotence identifier

Table 5 Response body parameters

Parameter

Type

Description

propagation

Propagation object

Propagation details

request_id

String

Request ID

Table 6 Propagation

Parameter

Type

Description

id

String

Unique association ID

project_id

String

Project ID

er_id

String

Enterprise router ID

route_table_id

String

Unique ID of the route table

attachment_id

String

Unique ID of the attachment

resource_type

String

  • Definition: Resource type.

  • Range:

    • vpc: VPC

    • vpn: VPN gateway

    • vgw: Direct Connect virtual gateway

    • peering: peering connection. A cloud connection is used to connect two enterprise routers from different regions to form a peering connection attachment.

    • gdgw: global DC gateway

resource_id

String

Unique ID of the attachment

state

String

  • Definition: Status.

  • Range:

    • pending

    • available

    • modifying

    • deleting

    • deleted

    • failed

created_at

String

Creation time. It is UTC time in the format of YYYY-MM-DDTHH:mm:ss.sssZ.

updated_at

String

Update time. It is UTC time in the format of YYYY-MM-DDTHH:mm:ss.sssZ.

Example Requests

Creating a route propagation

POST https://{erouter_endpoint}/v3/08d5a9564a704afda6039ae2babbef3c/enterprise-router/ad838a5e-dbef-22cc-b1d9-cb46bef77ae8/route-tables/915a14a6-867b-4af7-83d1-70efceb146f9/enable-propagations

{
  "attachment_id" : "a5b7d209-dc02-4c46-a51f-805eadd3de64"
}

Example Responses

Status code: 202

Accepted

{
  "propagation" : {
    "id" : "915a14a6-867b-4af7-83d1-70efceb146f9",
    "route_table_id" : "91c013e2-d65a-474e-9177-c3e1799ca726",
    "attachment_id" : "a5b7d209-dc02-4c46-a51f-805eadd3de64",
    "resource_type" : "vpc",
    "resource_id" : "4e5fe97c-82bc-432e-87d8-06d7e157dffa",
    "state" : "pending",
    "created_at" : "2020-03-11T15:13:31Z",
    "updated_at" : "2020-03-11T15:13:31Z"
  },
  "request_id" : "915a14a6-867b-4af7-83d1-70efceb146f9"
}

Status Codes

Status Code

Description

202

Accepted

Error Codes

See Error Codes.