Successful response codes
In addition to the rate limit information in the header, the APIs attempt to generate a response code and also include an appropriate explanation in a JSON body when necessary. For all codes greater than 200, clients should wait before attempting another connection.
HTTP return code on success
|GET /account/usage||200 OK|
|/push/delete||204 No content|
|/historics/start||204 No content|
|/historics/stop||204 No content|
|/historics/update||204 No content|
|/historics/delete||204 No content|
|/source/delete||204 No content|
Summary of the codes you might see
Response codes in the 400 range indicate an error with the client. Codes in the 500 range indicate a problem with the server.
The API call was successful.
You have successfully connected. This code is returned, for example, by the /source/create endpoint in our Managed Sources API and indicates that authentication has succeeded and you are logged in correctly to the data source that you want to filter in DataSift.
The API call was accepted. The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place
The server successfully processed the request, but is not returning any content.
4xx Client Error
400 Bad Request
Bad request from the client.
HTTP authentication failed due to a non-existent username or an incorrect API key.
Your account has been denied access due to a violation.
404 Not Found
- Streaming API: Invalid hash.
- REST API: endpoint not found.
405 Method Not Allowed
A request method is not supported for the requested resource; for example, a GET request on a form which requires data to be presented via POST, or a PUT request on a read-only resource.
Indicates that the request could not be processed because of conflict in the request, such as trying to start Historics query which is already running.
Indicates that the resource requested is no longer available and will not be available again, for example performing a GET request to retrieve details of an account identity which has been deleted.
413 Payload Too Large
The request is larger than the server is willing or able to process. An example of when you may receive this is when you exceed your per-minute ingestion limit on ODP.
415 Unsupported Media Type
The request entity has a media type which the resource does not support. For example, trying to create a PYLON analysis task using a media type other than
429 Too Many Requests
You have hit your API rate limit. Not supported by API versions prior to 1.2.
5xx Server Error
500 Server Internal Error
Try again. You shouldn't see this error. Please contact support.
503 Service Unavailable
Try again. The node you were routed to is unavailable.
504 Gateway Timeout
Try again. The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.