Skip to main content
Responses to Toku API calls use the HTTP status code convention to indicate whether the call was successful or failed.
200
Ok
The call was successful.
201
Created
The call was successful and a new object or group of objects was created.
400
Bad Request
The call is well formed but contains semantic errors. You may have missed required fields, or included fields that do not match.
401
Unauthorized
You did not enter the API Key in the Header of the call, or you did it with an incorrect format.
403
Forbidden
According to the API Key you indicated in the Header, you do not have permissions to make this type of call.
404
Not Found
According to the API Key indicated in the Header, the resource does not exist. This may also indicate that you are not allowed to make this type of call.
422
Unprocessable Entity
The call is well formed but contains semantic errors. You may have missed required fields, or included fields that do not match.
429
Too Many Requests
You called the API too many times in a row, wait a bit.
500
Internal Server Error
The server encountered an error while processing the request.
503
Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.
504
Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.
505
HTTP Version Not Supported
The server does not support, or refuses to support, the major version of HTTP that was used in the request message.