Documentation Index
Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt
Use this file to discover all available pages before exploring further.
Errors
The Collate API uses conventional HTTP response codes to indicate the success or failure of an API request. Error responses include a JSON body with details about what went wrong.HTTP Status Codes
Success Codes (2xx)
| Code | Description |
|---|---|
200 OK | Request succeeded |
201 Created | Resource created successfully |
202 Accepted | Request accepted for async processing |
204 No Content | Success with no response body |
Client Error Codes (4xx)
| Code | Error Type | Description |
|---|---|---|
400 | BAD_REQUEST | Invalid request parameters or malformed JSON |
401 | UNAUTHORIZED | Missing or invalid authentication token |
403 | FORBIDDEN | Valid token but insufficient permissions |
404 | ENTITY_NOT_FOUND | Requested resource doesn’t exist |
409 | ENTITY_ALREADY_EXISTS | Resource with same identifier exists |
409 | ENTITY_LOCKED | Entity is locked during deletion |
412 | PRECONDITION_FAILED | ETag mismatch on conditional update |
413 | BULK_LIMIT_EXCEPTION | Request payload exceeds size limits |
429 | LIMITS_EXCEPTION | Rate limit exceeded |
Server Error Codes (5xx)
| Code | Error Type | Description |
|---|---|---|
500 | INTERNAL_ERROR | Unexpected server error |
Error Types Reference
BAD_REQUEST
ENTITY_NOT_FOUND
ENTITY_ALREADY_EXISTS
UNAUTHORIZED
FORBIDDEN
PRECONDITION_FAILED
LIMITS_EXCEPTION
Handling Errors
Python SDK
Validation Errors
When request validation fails, the error message includes details about which field(s) failed:Retry Logic
For transient errors (5xx, 429), implement retry with exponential backoff:Debugging Tips
Validate request format
For 400 errors, check that all required fields are present and properly formatted.