Associate VPC
Updated at：2025-11-11
Description
The PrivateZone is associated with the VPC.
Request structure
Plain Text
1PUT /v{version}/privatezone/{zoneId}?{action}&clientToken={clientToken} HTTP/1.1
2Host: privatezone.baidubce.com
3Authorization: authorization string
4{
5 "region": {region},
6 "vpcIds": {vpcIds}
7} Request headers
There are no special headers required beyond the common headers.
Request parameters
| Parameter name | Types | Whether required | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | For API version No., the current value is 1 |
| zoneId | String | Yes | URL parameter | Zone ID |
| action | String | Yes | Query | bind |
| clientToken | String | No | Query | Idempotence token, which is an ASCII string with a length not exceeding 64 bits, see details in [ClientToken Idempotence Support](DNS/API Reference/General Description.md#Idempotence) |
| region | String | Yes | Request Body parameters | The region where the VPC to be bound or unbound belongs |
| vpcIds | Yes | Request Body parameters | List of IDs of the VPCs to be bound or unbound |
Response headers
No special headers are required beyond the standard ones.
Response parameters
There are no special response parameters
Request example
Plain Text
1PUT /v1/privatezone/zone-xktdeMSf?bind&clientToken=cecad37a-5a1e-4135-a1bc-b1a105d12dec HTTP/1.1
2Host: privatezone.baidubce.com
3Authorization: bce-auth-v1/c98fb9a1366011e8912505e5e0ae9978/2018-05-22T10:54:32Z/3600/host;x-bce-account;x-bce-client-ip;x-bce-date;x-bce-request-id;x-bce-security-token/e66be5966b6d6728d8f0431b0cd10558e8a69989cbddfc5e9211371fe05fa7e9
4{
5 "region": "bj",
6 "vpcIds": [
7 "vpc-h8jflr6n"
8 ]
9}Response example:
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 9d3e5721-d77f-4984-9fff-3092fa4e31a3
3Date:Fri, 17 Mar 2017 13:22:21 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS