Documentation REST API

REST API

Use structured errors and request IDs to recover safely.

Error responses explain the stable failure category without exposing private organization or service details.

Error shape

Record requestId in your own metadata-only diagnostics. Do not attach the submitted diff or access token to a support request.

json 
{
  "requestId": "123e4567-e89b-42d3-a456-426614174000",
  "error": {
    "code": "INVALID_DIFF",
    "message": "Diff could not be parsed as unified diff."
  }
}

HTTP statuses

  • 400 — malformed JSON or a request that does not match the schema.
  • 401 — missing, malformed, expired, or invalid bearer authentication.
  • 403 — account or review product access is unavailable.
  • 404 — organization is absent or intentionally hidden from this caller.
  • 413 — diff or context exceeds the configured payload limit.
  • 422 — the submitted text cannot be parsed as a unified diff.
  • 429 — a product or operational quota was exceeded, or an upstream model provider applied a rate limit.
  • 5xx — review dependency, timeout, configuration, or unexpected service failure.

Current limits

Diff input is limited to 256,000 UTF-8 bytes, context to 64,000 UTF-8 bytes, and maxFindings to a value from 1 through 100. Commercial limits can vary by provisioned entitlement.

Retry with intent

Correct 4xx input or access failures before retrying. For a 429, wait for retryAfterSeconds when it is present; otherwise use bounded backoff and stop repeated automatic retries. For repeated 5xx failures, stop automatic retries and contact support with requestId.

Documentation