> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zdlake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> Problem Details responses and recoverable error codes.

Zero returns errors as `application/problem+json`. The `code` is the stable machine-readable reason; `detail` explains this occurrence.

```json theme={null}
{
  "type": "https://docs.zdlake.com/api/errors#bad-request",
  "title": "Bad Request",
  "status": 400,
  "detail": "Invalid request parameters",
  "code": "VALIDATION_ERROR",
  "request_id": "req_01JABCD123",
  "errors": {
    "where": ["where may contain at most 20 conditions"]
  }
}
```

| Field | Description |
| - | - |
| `type` | Documentation URI for the problem class |
| `title` | Short HTTP-oriented summary |
| `status` | HTTP status code |
| `detail` | Human-readable explanation of this failure |
| `code` | Stable machine-readable reason |
| `request_id` | Request identifier for logs and support |
| `errors` | Field-level details when available |

## Bad request

Operations return `400` with either `VALIDATION_ERROR` or `BAD_REQUEST` when parameters, JSON, cursors, query conditions, or API versions are invalid. Fix the request before retrying.

## Unauthorized

A missing, malformed, expired, or revoked API key returns `401`. Provision or rotate the key, then retry with `Authorization: Bearer <key>`.

## Forbidden

A valid key without permission for an operation returns `403 FORBIDDEN`. Use a key with the required scope; repeating the same request with the same key will not succeed.

## Not found

Entity retrieval and source-record retrieval operations return `404 NOT_FOUND` when the requested identifier does not exist. Search operations return an empty `data` array instead.

## Internal server error

An unexpected failure returns `500 INTERNAL_ERROR`. Retry transient failures with bounded exponential backoff and jitter.

The readiness endpoint may also return `503` when a required database is unavailable.

## Rate limited

A request that exceeds its key's quota returns `429 RATE_LIMITED`. Wait for the number of seconds in `Retry-After` before retrying. See [Rate limits](https://docs.zdlake.com/api/rate-limits.md).

## Request IDs

Log the `request_id` from every failed response and include it when reporting an issue. The same value is returned in the `X-Request-Id` response header.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.