X-Auth-Token
HTTP
header. Customers obtain this token by first using the
Rackspace Cloud Authentication Service and supplying a
valid username and API access key. username
and
apiKey
. When you authenticate
successfully, the response to your authentication
request will include a catalog of the services to
which you have subscribed rather than the sample
values shown here.expires
attribute denotes the time
after which the token will automatically become
invalid. A token may be manually revoked before
the time identified by the expires
attribute; expires
predicts a token's
maximum possible lifespan but does not guarantee
that it will reach that lifespan. Clients are
encouraged to cache a token until it expires. jsmith
is the
administrative user for the account,
holding the fully-privileged
identity:admin
role.
Other users might hold other roles with
different privileges. Roles need not be
associated with actual job functions such
as Administrator, Operator, Developer,
Tester, or Trainer. type="compute"
,
identifying them as compute services even though the word "compute" does not appear in their names.
type="compute"
identifies all the
available compute services, one of which is named
cloudServers and one of which is named
cloudServersOpenStack. New compute service names may be added
in future releases; whatever the compute services are
named, you can always
recognize them by parsing for
type="compute"
in the authentication
response's service catalog. type="compute"
identifies
compute services such as cloudServers and
cloudServersOpenStack. Some developers have
found the service type attribute to be useful
in parsing the service catalog. For additional
information on Auth 2.0 (also known as the
Cloud Identity Service), refer to the
Region | Endpoint | |||||
Chicago (ORD) | https://ord.databases.api.rackspacecloud.com/v1.0/ |
|||||
Dallas/Ft. Worth (DFW) | https://dfw.databases.api.rackspacecloud.com/v1.0/ |
|||||
London (LON) |
https://lon.databases.api.rackspacecloud.com/v1.0/ |
publicURL
field returned
by the authentication response. For example, in publicURL
field for
cloudServers
("https://servers.api.rackspacecloud.com/v1.0/Content-Type
header
and is Accept
header or by adding an
.xml
or .json
extension
to the request URI. Note that it is possible for a
response to be serialized using a format different
from the request. If no response format is specified,
JSON is the default. If conflicting formats are
specified using both an Accept
header and
a query extension, the query extension takes
precedence.Format | Accept Header | Query Extension | Default |
JSON | application/json | .json | Yes |
XML | application/xml | .xml | No |
ATOM | application/atom+xml | .atom | No |
Attribute | Description | |||
jobId | An identifier for the specific request. | |||
callbackUrl | Resource locator for querying the status of the request. |
Accept-Encoding
header on the request from the client and indicated
by the Content-Encoding
header in the server response. Unless the
header is explicitly set, encoding defaults to disabled. Header Type | Name | Value |
HTTP/1.1 Request | Accept-Encoding |
gzip |
HTTP/1.1 Response | Content-Encoding |
gzip |
Verb | URI | RegEx | Default | ||
&GET; changes-since | */instances/* | ^/vd+.d+/instances.* | 3/minute | ||
&POST; | */instances/* | ^/vd+.d+/instances.* | 10/minute | ||
&POST; instances | */instances/* | ^/vd+.d+/instances.* | 50/day | ||
&PUT; | */instances/* | ^/vd+.d+/instances.* | 10/minute | ||
&DELETE; | */instances/* | ^/vd+.d+/instances.* | 100/minute |
Retry-After
header to
notify the client when it can attempt to try
again. Name | Description | Limit | ||
Instances | Maximum number of instances allowed for your account | 5 | ||
Volume Size | Maximum volume size per instance in gigabytes (GB) for your account | 50 |
Code | Description |
yyyy | Four digit year |
MM | Two digit month |
dd | Two digit day of month |
T | Separator for date/time |
HH | Two digit hour of day (00-23) |
mm | Two digit minutes of hour |
ss | Two digit seconds of the minute |
SSS | Three digit milliseconds of the second |
Z | RFC-822 timezone |
?limit=10&marker=1234
. Items are
displayed sorted by ID. {"href": "<url>", "rel": "next"}
.
Any response that is truncated by pagination will have
a ?limit=2
), so the responses
that follow each show 2 instances and return a
?marker=4137d6a4-03b7-4b66-b0ef-8c7c35c470d3
).
Also a link is provided to retrieve the next 2 results
(limit=2
) in the link element
identified by the attribute rel="next"
(XML) or "rel":"next"
(JSON):badRequest
unauthorized
forbidden
itemNotFound
badMethod
overLimit
details
element for more specifics. Contact support
if you think you need higher request rate limits.badMediaType
unprocessableEntity
instanceFault
notImplemented
serviceUnavailable
instanceFault
examples show errors when the server has erred or
cannot perform the requested operation:code
) is returned in the body of the response for
convenience. The message
element returns a human-readable message that
is appropriate for display to the end user. The details
element is
optional and may contain information that is useful for tracking down an error, such
as a stack trace. The details
element may or may not be appropriate for
display to an end user, depending on the role and experience of the end user.instanceFault
) may change depending
on the type of error. badRequest
examples
show errors when the volume size is invalid:itemNotFound
errors: