Sign in
Virtual Cross Connects

Update the Virtual Cross Connect

Update the Virtual Cross Connect.<br /><br />Cloud IPs can only be patched during the created state, as GCE will only inform you of your generated IP once the pending connection requested has been accepted. Once the Virtual Cross Connect has moved to provisioning, the IPs can no longer be patched.<br /><br />Once the Virtual Cross Connect has moved to provisioned and you are ready to enable routing, you can toggle the routing announcements to true.

patch/virtual_cross_connects/{id}

Path parameters

idstring uuid required
Example:6a09cdc3-8948-47f0-aa62-74ac943d6c58

Identifies the resource.

Request body

primary_cloud_ipstring

The IP address assigned for your side of the Virtual Cross Connect.<br /><br />If none is provided, one will be generated for you.<br /><br />This value can not be patched once the VXC has bene provisioned.

primary_enabledboolean

Indicates whether the primary circuit is enabled. Setting this to false will disable the circuit.

primary_routing_announcementboolean

Whether the primary BGP route is being announced.

secondary_cloud_ipstring

The IP address assigned for your side of the Virtual Cross Connect.<br /><br />If none is provided, one will be generated for you.<br /><br />This value can not be patched once the VXC has bene provisioned.

secondary_enabledboolean

Indicates whether the secondary circuit is enabled. Setting this to false will disable the circuit.

secondary_routing_announcementboolean

Whether the secondary BGP route is being announced.

Example request

{
  "primary_cloud_ip": "169.254.0.2",
  "primary_enabled": true,
  "secondary_cloud_ip": "169.254.0.4",
  "secondary_enabled": true
}

Response

Successful response

Example response

{
  "data": {
    "created_at": "2018-02-02T22:25:27.521Z",
    "id": "6a09cdc3-8948-47f0-aa62-74ac943d6c58",
    "record_type": "virtual_cross_connect",
    "updated_at": "2018-02-02T22:25:27.521Z",
    "name": "test interface",
    "network_id": "6a09cdc3-8948-47f0-aa62-74ac943d6c58",
    "status": "provisioned",
    "bandwidth_mbps": 50,
    "bgp_asn": 1234,
    "cloud_provider": "aws",
    "cloud_provider_region": "us-east-1",
    "primary_bgp_key": "yFV4wEPtPVPfDUGLWiyQzwga",
    "primary_cloud_account_id": "123456789012",
    "primary_cloud_ip": "169.254.0.2",
    "primary_enabled": true,
    "primary_telnyx_ip": "169.254.0.1",
    "secondary_bgp_key": "ge1lONeK9RcA83uuWaw9DvZy",
    "secondary_cloud_ip": "169.254.0.4",
    "secondary_enabled": true,
    "secondary_telnyx_ip": "169.254.0.3",
    "region_code": "ashburn-va",
    "region": {
      "code": "ashburn-va",
      "name": "Ashburn",
      "record_type": "region"
    }
  }
}

Changes

Changed in 2 of the 61 revisions of this API.4

  • 1571b0380bd72See the full diff
    • ▲

      the errors/items/code response's property type/format changed from integer/int32 to string/ for status 422

      response-property-type-changed

    • ▲

      the errors/items/code response's property type/format changed from integer/int32 to string/ for status default

      response-property-type-changed

    This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 8f5f4e5379942See the full diff
    • ▲

      the errors/items/code response's property type/format changed from string/ to integer/int32 for status 422

      response-property-type-changed

    • ▲

      the errors/items/code response's property type/format changed from string/ to integer/int32 for status default

      response-property-type-changed

    This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog