HTTP Response Codes

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

validate 200 OK
compile 200 OK
usage 200 OK
dpu 200 OK
balance 200 OK
push/validate 200 OK
push/create 200 OK
push/pause 200 OK
push/resume 200 OK
push/update 200 OK
push/stop 200 OK
push/delete 204 No content
push/log 200 OK
push/get 200 OK
pull 200 OK
historics/prepare 200 OK
historics/start 204 No content
historics/stop 204 No content
historics/status 200 OK
historics/update 204 No content
historics/delete 204 No content
historics/get 200 OK
preview/create 202 Accepted
preview/get 202 OK
source/create 201 Created
source/validate Not available yet
source/stop 200 OK
source/start 200 OK
source/update 202 Accepted
source/delete 204 No content
source/get 200 OK
source/log 200 OK

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.

200 OK

The API call was successful.

201 Created

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.

202 Accepted

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

204 Success

The server successfully processed the request, but is not returning any content.

400 Bad Request

Bad request from the client.

401 Unauthorized

HTTP authentication failed due to a non-existent username or an incorrect API key.

403 Forbidden

Your account has been denied access due to a violation.

404 Unknown

  • Streaming API: Invalid hash.
  • REST API: endpoint not found.

429 Too Many Requests

You have hit your API rate limit. Not supported by API versions prior to 1.2.

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.