Skip to main content
The Chameleon API is robust with 99.99% uptime and extensive monitoring. In case you are facing any error, you can check our Status Page.

​
Status Code 403

Account token is not valid or has been revoked 
{
  "code": 403,
  "messages": ["Unauthorized: Please check your Chameleon Account Secret"]
}

​
Status Code 404

Endpoint or Resource not found 404’s happen for a couple of reasons:
  • The URL was not pasted correctly from these docs. URLs have an environment specifier directly after the version, make sure to include this
  • A resource/collection you tried to access is not found for this Secret token
{
  "code": 404,
  "messages": ["Endpoint not found: Please recheck with the API docs https://developers.chameleon.io"]
}

​
Status Code 409

Conflicting state of the Resource
  • The Tour is not live when trying to create a Delivery
  • The specified update is not compatible with the current state of the Model
  • The Delivery has already been triggered when the until time is updated
{
  "code": 409,
  "messages": ["Conflict: Please check the preconditions in the API docs https://developers.chameleon.io"]
}

​
Status Code 422

The request parameters cannot be processed as-is
  • The parameter that is specifies a timestamp cannot be parsed/interpreted as a timestamp
  • The identifier is missing when looking up a User Profile
{
  "code": 422,
  "messages": ["Unprocessable: Please check the request parameters with the API docs https://developers.chameleon.io"]
}

​
Status Code 429

You have made too many concurrent or bucketed requests and exceeded your Rate limit. See also Rate limiting
  • Headers
X-Ratelimit-Wait: 114
X-Ratelimit-Limit: 2
  • Body
{
  "code": 429,
  "messages": ["Rate Limited: Please refer to the API docs https://developers.chameleon.io/concepts/rate-limiting for more information"],
  "wait": 14
}

​
Status Code 500

Server error An Internal server error occurred (one that we otherwise had not planned on receiving). Typically these issues stem from downstream issues such as when a database is in the middle of failing over, an External dependency cannot be met temporarily or less often our code is not working 
{
  "code": 500,
  "messages": ["Internal server error: Please retry later"]
}

​
Status Code 503

Server not available or backend didn’t respond in time — possibly not a JSON response depending on the origin of the 503 Unexpected maintenance, API downtime or the inability to shed enough load with Rate limiting 
{
  "code": 503,
  "messages": []
}

​
Status Code 504

The Server contacted or proxied your request to a different Service which took too long to respond This can happen when a request is too complex or the system load is too high. You may retry your request again after a suitable delay. 
{
  "code": 504,
  "messages": ["Internal timeout: An internal operation took too long."]
}