Errors

Corinthian does not document one rigid shared error envelope across every endpoint. Integrations should rely on:

• the HTTP status code
• the returned message
• any field-level validation details included by the endpoint

Practical Handling Rules

• treat 401 and 403 as authentication or permission problems
• treat 404 as a missing resource or endpoint
• treat 422 or validation failures as request-shape problems
• treat 429 as a rate-limit response and back off
• log the server message and request identifier when available

Guidance

• do not hardcode one old error.type/error.code envelope across the entire API
• show validation messages to users or admins when the endpoint returns them
• build retry logic around status codes, not prose alone

Related Pages

• Authentication
• Rate Limits