What do the response codes mean?

Our API uses conventional HTTP response codes to indicate success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error from information provided as part of the request (e.g. the requested object doesn't exist, an invalid setting, etc.), and codes in the 5xx range indicate an error on our end.

The response of all API errors contain a message parameter which has developer-facing information about why the request failed.

See the table below for a list of error codes and their corresponding descriptions:

Code	Summary	Description
200	OK	The request completed successfully
400	Bad Request	Request is missing or has a bad parameter.
400	Bad Request	Request is missing or has an invalid API key.
401	Not Authorized	Key is valid, but account does not have permissions to perform this action.
403	Forbidden	Request is missing or has an invalid API key.
404	Not Found	The requested resource doesn't exist.

What about rate limits?

All of these endpoints are rate limited. You should be sure to check the response codes and retry requests that exceed the rate limit at a later time. If you hit rate limits, we recommend adjusting your request-rate using an exponential backoff.