Developer resources v1
Coilinx API
Read-only inventory sync and signed operational webhooks.
Errors
Errors use JSON with a stable machine-readable code and request ID.
{
"error": "INVALID_API_KEY",
"message": "Invalid API key.",
"requestId": "req_01abc"
}
Include requestId when contacting Coilinx support. Never include your API key.
Status codes
| Status | Meaning | Recommended action |
| --- | --- | --- |
| 400 | Invalid parameter, cursor, timestamp, or filter | Correct the request; do not retry unchanged |
| 401 | Missing, malformed, revoked, or unknown API key | Replace or rotate the key |
| 403 | Company inactive, Pro access unavailable, or scope denied | Check billing and key permissions |
| 404 | Resource does not exist in the authenticated company | Remove or reconcile the local record |
| 405 | The endpoint does not support that HTTP method | Use the documented GET method |
| 429 | Per-key rate limit exceeded | Honor Retry-After and back off |
| 500 | Unexpected server error | Retry with exponential backoff |
Error codes
| Code | Description |
| --- | --- |
| INVALID_API_KEY | Bearer key is invalid or revoked |
| FEATURE_LOCKED | Company does not have Pro API access |
| COMPANY_ACCESS_BLOCKED | Company or billing status is inactive |
| INSUFFICIENT_SCOPE | Key lacks the required scope |
| RATE_LIMIT_EXCEEDED | Too many requests in the current minute |
| REQUEST_FAILED | Validation or routing failure |
| INTERNAL_ERROR | Unexpected platform failure |
Treat unknown error codes according to their HTTP status so future additions do not break your integration.