Skip to content

Errors

The API returns standard HTTP status codes with a JSON body. Every error body has a detail field. Other fields depend on where the error came from.

Code Meaning
400 The request was malformed or failed a rule.
401 Missing, expired, or invalid token or API key. Authenticate again.
403 Valid credentials, but your role does not permit this action.
404 The record does not exist or is not visible to your company.
409 The action conflicts with the record’s state, for example a pipeline move that needs a recorded decision first.
413 An uploaded file is too large.
422 The request body or query failed validation.
429 Rate limited. See Rate Limits.
500 Server error. Retry with backoff, and report it if it persists.
503 The feature is switched off or temporarily unavailable. The detail says which.
  • Most errors: {"detail": "Not authenticated"}.
  • Validation (422): detail is a list. Each entry names the field in loc, a message in msg and the rule in type.
  • Coded errors: {"detail": "...", "code": "GC-10000", "resolution": "..."}. The code is stable and resolution says what to do. Codes are grouped by area, for example GC-11xxx for sign-in and sessions and GC-15xxx for contracts.
  • Unhandled errors: {"detail": "...", "error": "...", "status_code": 500, "request_id": "..."}. A server error (5xx) also carries a short reference. Quote it, or the request_id, when you contact support.
  • Rate limited (429): {"detail": "Rate limit exceeded", "limit": "..."} with a Retry-After header.

A 404 can mean the record does not exist or that it belongs to another company. The platform deliberately does not say which, to avoid confirming the existence of other customers’ data.