Error handling

How to handle response codes

The API returns standard HTTP status codes to indicate success or failure:

  • 200 OK – Request succeeded

  • 201 Created – Resource successfully created

  • 400 Bad Request – Invalid input or parameters

  • 401 Unauthorized – Missing or invalid API key

  • 403 Forbidden – You don't have permission to perform this action

  • 404 Not Found – Resource does not exist

  • 429 Too Many Requests – Rate limit exceeded

  • 500 Internal Server Error – Something went wrong on our end

Error responses include a JSON payload with a message field explaining what went wrong. Make sure your integration handles these errors gracefully and logs or displays useful feedback to users where appropriate.

Last updated