Service access endpoints#

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

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


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

Regionalized service endpoints#



Chicago (ORD)

Chicago (ORD) snet

Dallas/Ft. Worth (DFW)

Dallas/Ft. Worth (DFW) snet

Northern Virginia (IAD)

Northern Virginia (IAD) snet

London (LON)

London (LON) snet

Sydney (SYD)

Sydney (SYD) snet

Hong Kong (HKG)

Hong Kong (HKG) snet

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 endpoints are prefixed with snet in the “Regionalized service endpoints” table above. ServiceNet is the data center internet network. In your authentication response, 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.


You should copy the base URLs directly from the catalog rather than trying to construct them manually.

The Identity service returns an endpoint with your account ID. Note the following information about account ID:

  • Account ID from Identity is the same as the Project ID given by the X-Project-ID header set. (You might also see account ID or project ID referred to as tenant ID.)

  • You do not have to provide the account ID for the Cloud Queues API if you have the X-Project-ID header set. (In this case, the Cloud Queues API works with or without the accout ID specified.)

  • Without the X-Project-ID header, you receive an auth error if the account ID is not in the URL.

  • If the account ID is in the URL, the Cloud Queues API will use that ID in place of the X-Project-ID header.

  • Account ID and Project ID refer to your Rackspace account number.