Schemas

Unique identifier of the dedicated connection. (UUID format)

Project ID. (UUID format)

Organization ID. (UUID format)

Status of the dedicated connection.

Name of the dedicated connection.

List of tags associated with the dedicated connection.

ID of the PoP where the dedicated connection is located. (UUID format)

Bandwidth size of the dedicated connection.

Size of the links supported on this dedicated connection.

Creation date of the dedicated connection. (RFC 3339 format)

Last modification date of the dedicated connection. (RFC 3339 format)

Demarcation details required by the data center to set up the supporting Cross Connect. This generally includes the physical space in the facility, the cabinet or rack the connection should land in, the patch panel to go in, the port designation, and the media type.

Range in which to pick vlan for self-hosted links on this dedicated connection. Both start & end are included. Any range defined here must be itself included in the greater allowed range of vlans from 1500 to 3899 (this range is hardware dependent and can change over time, but actual range will be enforced).

Region of the dedicated connection.

Unique identifier of the link. (UUID format)

Project ID. (UUID format)

Organization ID. (UUID format)

Name of the link.

List of tags associated with the link.

ID of the PoP where the link's corresponding connection is located. (UUID format)

Rate limited bandwidth of the link.

Status of the link.

Status of the link's BGP IPv4 session.

Status of the link's BGP IPv6 session.

ID of the Scaleway VPC attached to the link. (UUID format)

Defines whether route propagation is enabled or not. To enable or disable route propagation, use the dedicated endpoint.

Creation date of the link. (RFC 3339 format)

Last modification date of the link. (RFC 3339 format)

Partner host information.

Self-host information.

VLAN of the link.

BGP configuration on Scaleway's side.

BGP configuration on peer's side (on-premises or other hosting provider).

ID of the routing policy IPv4 attached to the link. (UUID format)

ID of the routing policy IPv6 attached to the link. (UUID format)

Region of the link.

List of connections on current page.

Total number of connections returned.

List of links on the current page.

Total number of links.

List of partners on current page.

Total number of partners returned.

List of PoPs on the current page.

Total number of PoPs.

Unique identifier of the partner. (UUID format)

Name of the partner.

Contact email address of partner.

Image URL of the partner's logo.

URL of the partner's portal.

Creation date of the partner. (RFC 3339 format)

Last modification date of the partner. (RFC 3339 format)

Unique identifier of the PoP. (UUID format)

Name of the PoP. It is the common reference of Hosting DC (ex: TH2).

Name of the PoP's hosting provider, e.g. Telehouse for TH2 or OpCore for DC3.

Physical address of the PoP.

City where PoP is located.

Image URL of the PoP's logo.

Available bandwidth in Mbits/s for future hosted links from available connections in this PoP.

Pretty name of the PoP. Includes name, hosting provider and location information (ex: Paris - TeleHouse TH2).

Region of the PoP.

Unique identifier of the routing policy. (UUID format)

Project ID. (UUID format)

Organization ID. (UUID format)

Name of the routing policy.

List of tags associated with the routing policy.

IP prefixes to accept from the peer (ranges of route announcements to accept). (IP network)

IP prefix filters to advertise to the peer (ranges of routes to advertise). (IP network)

Creation date of the routing policy. (RFC 3339 format)

Last modification date of the routing policy. (RFC 3339 format)

IP prefixes version of the routing policy.

Region of the routing policy.