vpc · 2017-03-12

CreateVpc

POST

Create a VPC instance.

Wire call

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

Request parameters

Field	Type	Required	Description
VpcName	string	Yes	The VPC name. The maximum length is 60 bytes.
CidrBlock	string	Yes	VPC CIDR block, which must fall within the following three private network IP ranges: 10.0.0.0/12, 172.16.0.0/12, and 192.168.0.0/16.
EnableMulticast	string	No	Whether multicast is enabled. `true`: Enabled. `false`: Not enabled.
DnsServers	string[]	No	DNS address. A maximum of 4 addresses is supported.
DomainName	string	No	Domain name of DHCP
Tags	Tag[]	No	Bound tags, such as [{"Key": "city", "Value": "shanghai"}]
EnableRouteVpcPublish	boolean	No	Vpc association with CCN route publish policy. true: enables cidr route publishing. false: enables subnet route publishing. default is subnet route publishing when creating a vpc. to select cidr route publishing, submit a ticket for adding to allowlist.

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
Vpc	Vpc	The VPC object.
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": {
    "Vpc": …,
    "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 · CreateVpc

{
  "VpcName": "<VpcName>",
  "CidrBlock": "<CidrBlock>"
}

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

Recorded example response — captured 2026-09-17

{
  "Response": {
    "Vpc": {
      "VpcName": "example-network",
      "VpcId": "vpc-5gqs921z",
      "CidrBlock": "10.200.0.0/16",
      "IsDefault": false,
      "EnableMulticast": false,
      "EnableDhcp": true,
      "EnableRouteVpcPublish": false,
      "CreatedTime": "0000-00-00 00:00:00",
      "Region": "luzon",
      "IsShare": false,
      "Ipv6CidrBlockSet": [],
      "CdcId": "",
      "EnableCdcPublish": false,
      "DhcpOptionsId": "dopt-6m95zzxy",
      "DnsServerSet": [
        "183.60.83.19",
        "183.60.82.98"
      ],
      "DomainName": "",
      "TagSet": []
    },
    "RequestId": "80793df9-acda-11dc-5a17-5b097b67b092"
  }
}

Behaviour

A default route table is created alongside the VPC.