Response codes

Rackspace Ticketing API returns an HTTP code that denotes the type of response.

  • Successful response codes are returned only if all configured providers were successful in processing the request.
  • Error response codes are accompanied by an application/json response body that contains the error messages.

This API uses standard HTTP 1.1 response codes.

The following table lists possible responses with their associated codes and descriptions.

ResponseResponse codeDescription
OK200The request has succeeded. Some API calls return 201 instead.
Created201The request has succeeded. Some API calls return 200 instead.
No content204The request has been fulfilled but does not return a representation (that is, the response is empty).
Bad request400The request was not understood or was missing required parameters.
Unauthorized401Authentication failed, or the user does not have permissions for a requested operation.
Forbidden403The server understood the request but refused to fulfill it.
Not found404A requested resource was not found.
Method not allowed405The request method is not supported for this resource.
Too many requests429Too many requests have been sent in a given amount of time. Pause requests, wait up to one minute, and try again. Intended for use with rate limiting.
Internal Server Error500The service encountered an unexpected condition that prevented it from fulfilling the request.
Service Unavailable503The service is temporarily unavailable, for example, for scheduled platform maintenance. Try again later.

Example: Error message example

HTTP/1.1 400 Bad Request
Content-Type: application/json

"status": 400,
"message": "Category provided is invalid",
"faultCode": "badRequest",
"moreInfo": "docs/ticketing/general-api-info/faults/#badRequest"