vpc · 2017-03-12

CreateRouteTable

POST

Create a route table.

Wire call

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

Request parameters

Field	Type	Required	Description
VpcId	string	Yes	The ID of the VPC instance to be operated on. You can obtain the parameter value from the VpcId field in the returned result of DescribeVpcs API.
RouteTableName	string	Yes	The route table name. The maximum length is 60 characters.
Tags	Tag[]	No	Bound tags, such as [{"Key": "city", "Value": "shanghai"}].

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
RouteTable	RouteTable	Route table 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": {
    "RouteTable": …,
    "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 · CreateRouteTable

{
  "VpcId": "<VpcId>",
  "RouteTableName": "<RouteTableName>"
}

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

Recorded example response — captured 2026-09-17

{
  "Response": {
    "RouteTable": {
      "RouteTableId": "rtb-90dtbn2g",
      "VpcId": "vpc-5gqs921z",
      "RouteTableName": "example-network",
      "AssociationSet": [],
      "RouteSet": [],
      "Main": false,
      "CreatedTime": "0000-00-00 00:00:00",
      "Region": "luzon",
      "LocalCidrForCcn": [],
      "TagSet": []
    },
    "RequestId": "ca171a4f-37c8-9fbf-860c-d477f1d27e61"
  }
}

Behaviour

Separate from the default route table created with the VPC.