vpc · 2017-03-12

ModifyVpcAttribute

POST

Modify VPC attributes.

Wire call

Converge Cloud is RPC over HTTP. There is one path — / — and the action travels in the X-TC-Action header. The /vpc/ModifyVpcAttribute 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: ModifyVpcAttribute' \
  -H 'X-TC-Version: 2017-03-12' \
  -H 'X-TC-Timestamp: <unix-seconds>' \
  -H 'X-TC-Region: luzon' \
  -d '{"VpcId":"<VpcId>"}'

Request parameters

Field	Type	Required	Description
VpcId	string	Yes	VPC instance ID, in the format of vpc-f49l6u0z.
VpcName	string	No	VPC can be named freely, but the maximum length is 60 characters.
EnableMulticast	string	No	Whether multicast is enabled. `true`: Enabled. `false`: Off.
DnsServers	string[]	No	DNS address. A maximum of 4 addresses is supported. The first one is primary server by default, and the rest are secondary servers.
DomainName	string	No	Domain name
EnableRouteVpcPublish	boolean	No	Vpc association with CCN route publish policy. true enables cidr route publishing. false enables subnet route publishing. the default is subnet route publishing when creating a vpc. to use cidr route publishing, submit a ticket to add to allowlist.
EnableCdcPublish	boolean	No	Whether to publish the CDC subnet to CCN. `true`: Publish; `false`: Do not publish

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.

Field	Type	Description
RequestId	string	The 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": {
    // action-specific fields,
    "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.

SecretIdSecretKey

Request bodyvalid JSONPOST vpc.api3.convergecloud.com · ModifyVpcAttribute

{
  "VpcId": "<VpcId>"
}

This action changes resources in my own account and may create a charge. I understand.

Recorded example response — captured 2026-09-16

{
  "Response": {
    "RequestId": "e24e1a21-68db-1521-6baf-f3da820c8099"
  }
}