HTTP status codes

iLive uses standard HTTP status codes. The short catalogue:

Status	Meaning in the iLive API
200 OK	Request succeeded; body contains the result.
201 Created	A new resource was created (e.g. a collection, an indexed face).
204 No Content	Request succeeded, no body (e.g. after a delete).
400 Bad Request	Malformed request — bad field values, invalid IDs, invalid params.
401 Unauthorized	API key missing or invalid. See API keys.
403 Forbidden	Account is not active or the key is not allowed to use the endpoint.
404 Not Found	Target resource (collection, face, session) does not exist.
409 Conflict	Resource already exists — most commonly on collection creation.
413 Payload Too Large	Uploaded image is larger than 8 MB.
422 Unprocessable Entity	Semantic failure — e.g. no face detected in the uploaded image.
429 Too Many Requests	Rate limit exceeded. Back off with jitter — see Rate limits.
500 Internal Server Error	Unexpected server-side failure. Retry with backoff; contact support if it persists.
502 Bad Gateway	Upstream component unavailable — usually transient during deploys. Retry.
503 Service Unavailable	Temporary overload or maintenance. Retry with exponential backoff.

Each 4xx response carries a machine-readable code in the body — see Error codes for the full list.