Error Codes
4xx Client Errors
400 Bad Request
The request was invalid or cannot be otherwise served. This is usually caused by a missing required parameter or an invalid parameter.
We will normally return a more specific error message that can help you fix the issue.
401 Unauthorized
The request requires user authentication. This is usually caused by a missing or invalid API key.
402 Payment Required
The request requires a payment to be made. This is usually caused by a missing or invalid payment method.
We usually notify you well in advance of shutting off service for non-payment, however we reserve the right to do so if we are unable to reach you and an outstanding balance is not cleared promptly.
403 Forbidden
The request is forbidden. This is usually caused when the request has a valid API key, but the resource or action is not accessible to the API key.
404 Not Found
The requested resource was not found. This is usually caused by a missing or invalid resource ID.
405 Method Not Allowed
The request method is not allowed. Many endpoints support a subset of HTTP methods, and will return this error if the requested method is not supported.
408 Request Timeout
The request took too long to complete. This is usually caused by a slow network connection or a slow server.
410 Gone
The requested resource is no longer available. This is usually caused by a resource that has been deleted or expired.
413 Payload Too Large
The request payload is too large. This is usually caused by a large file or a large number of parameters.
You are most likely to see this when uploading a file.
Switching to HTTP/2 or upgrading your client lifts most restrictions on payload size.
429 Too Many Requests
The request was rate limited. This is usually caused by a high rate of requests in too short a period of time.
5xx Server Errors
500 Internal Server Error
The server encountered an error and was unable to process the request. This is usually caused by a bug in the server or an unexpected error on our side.
If you encounter this error, please contact support and we will immediately look into it.
502 Bad Gateway
The server received an invalid response from a downstream server. This is usually caused by a problem with a downstream server.
503 Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
More Docs coming soon
We're currently updating this page with the most up-to-date info. Thanks for your patience!