HTTP status codes

Summary of the HTTP status codes returned by the LX CloudPos API and the recommended action for each. For retry logic, see retry strategies.

Code	Meaning	Retry?	Action
`200`	OK	—	Consume the response.
`201`	Created	—	Document issued and queued.
`202`	Accepted (asynchronous processing)	—	Wait for the webhook or poll.
`204`	OK, no body	—	Operation succeeded.
`400`	Bad Request (validation)	No	Fix the body.
`401`	Unauthorized	No	Check the API key.
`403`	Forbidden	No	The required scope is missing.
`404`	Not Found	No	Check the key or the resource.
`409`	Conflict	No	`Idempotency-Key` reused with a different body.
`413`	Payload Too Large	No	Reduce the body below 256 KB.
`415`	Unsupported Media Type	No	Use `Content-Type: application/json`.
`422`	Unprocessable Entity	No	Domain validation failed.
`429`	Too Many Requests	Yes	Respect the `Retry-After` header.
`500`	Internal Server Error	Yes	Exponential backoff.
`501`	Not Implemented	No	Feature not available.
`502`	Bad Gateway	Yes	Backoff.
`503`	Service Unavailable	Yes	Aggressive backoff.
`504`	Gateway Timeout	Yes	Backoff.