Service access endpoints

The Rackspace Cloud Networks API service is a regionalized service. It allows the caller to select the region into which a load balancer is provisioned.

If you are working with cloud servers that are in one of the Rackspace data centers, using the ServiceNet endpoint in the same data center has no network costs and provides a faster connection. ServiceNet is the data center internet network. In your authentication response service catalog, it is listed as InternalURL.

If you are working with servers that are not in one of the Rackspace data centers, you must use a public endpoint to connect. In your authentication response, public endpoints are listed as publicURL. If you are working with servers in multiple data centers or have a mixed environment where you have servers in your data centers and in Rackspace data centers, use a public endpoint because it is accessible from all the servers in the different environments.

The following table lists the Cloud Networks endpoints that are available for each region.

Tip

To help you decide which regionalized endpoint to use, read about special considerations for choosing a region.

Regionalized service endpoints

Region	Endpoint
Chicago (ORD)	https://ord.networks.api.rackspacecloud.com/v2.0/
Dallas/Ft. Worth (DFW)	https://dfw.networks.api.rackspacecloud.com/v2.0/
Northern Virginia (IAD)	https://iad.networks.api.rackspacecloud.com/v2.0/
London (LON)	https://lon.networks.api.rackspacecloud.com/v2.0/
Sydney (SYD)	https://syd.networks.api.rackspacecloud.com/v2.0/
Hong Kong (HKG)	https://hkg.networks.api.rackspacecloud.com/v2.0/

The service catalog returned in the authentication response specifies the correct service access endpoint for your account to use for accessing Cloud Networks. Use the service type (rax:load-balancer) to locate the correct endpoint in the service catalog. For an example of the service catalog, see authentication response examples.