Errors and Statuses

Use HTTP code + response body + job status to drive client behavior.

Common HTTP Codes

Code	Meaning	Client Action
200	Successful read/update	Continue
201	Resource created	Continue
204	Deleted successfully (no body)	Continue
400	Invalid payload	Fix request data
401	Missing/invalid credentials	Replace or reissue API token
403	Access denied by plan/scope	Contact Nextry support
404	Resource not found	Check history_item_id
422	Validation error	Fix request params/body
429	Rate limit exceeded	Retry with backoff
500	Internal processing error	Retry later, escalate if persistent

Job Status Lifecycle

pending -> complete
pending -> error

Example:

• Status check example

Retry Guidance

• Retry 429 and 5xx with exponential backoff.
• Do not retry 400 without payload changes.
• On 401, check token format/scope and request token reissue from support if needed.
• For error jobs, log history_item_id and server error details for support.

Example:

• Generation request example
• History list example

Operational Logging

For production troubleshooting, log:

• Request timestamp (UTC)
• Endpoint and method
• history_item_id (if assigned)
• HTTP code
• Error message/body snippet

Example Links

• Create generation (retry strategy applies): POST /generation/generate_image_v2/ examples
• Check status: GET /user/generation-history/:id examples
• List history: GET /user/generation-history examples