Chapter 5. Service Access/Endpoints

Specify a region to operate against by selecting an endpoint from the table below to use for your Cloud Load Balancer API calls.


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

Table 5.1. Regionalized Service Endpoints
Region Endpoint
Chicago (ORD)
Dallas/Ft. Worth (DFW)
Northern Virginia (IAD)
London (LON)
Sydney (SYD)
Hong Kong (HKG)

Since you are load balancing Cloud Servers in this guide, you can determine the appropriate endpoint to select by viewing your Cloud Servers list and creating a load balancer within the same region as the datacenter in which your Cloud Server resides. When your resources reside in the same region as your load balancer, devices are in close proximity to each other and can take advantage of ServiceNet connectivity for free data transfer between services.


All examples in this guide assume that you are operating against the DFW datacenter, however if you are using a different datacenter, be sure to use the associated endpoint from the table above instead.

Replace the sample account ID number, 1234, with your actual account number returned as part of the authentication response. Use your actual account number wherever you see the field your_acct_id specified in this guide. Refer to Chapter 4, Generate an Authentication Token.

When making a Cloud Load Balancers API call, place the endpoint at the beginning of the request URL, for example: (, as you can see in the cURL Create Load Balancer Request examples in Chapter 6, Create a Load Balancer. Note that the v1.0 component in the URL indicates that you are using version 1.0 of the Cloud Load Balancers API.