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

# Legacy Errors

> Find error responses and retry rules for older routes.

## Legacy errors

Unversioned routes and replaced legacy routes keep their existing error formats. See [Current APIs](https://docs.sixtyfour.ai/api-reference/current.md) and [Legacy](https://docs.sixtyfour.ai/api-reference/legacy.md).

```json theme={null}
{
  "detail": "Insufficient API credits",
  "code": "payment_required",
  "correlation_id": "enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21"
}
```

Legacy `detail` can be a string, a list of validation errors, or an object. `code` is the legacy error classification, not `error_code`. `correlation_id` matches `X-Correlation-ID`. Some responses also include `feedback` with reporting instructions.

Feedback routes return `detail` and `error_code` without the `/v1` envelope's other fields.

| Status | Legacy code |
| - | - |
| 400 | `bad_request` |
| 401 | `unauthenticated` |
| 402 | `payment_required` |
| 403 | `forbidden` |
| 404 | `not_found` |
| 409 | `conflict` |
| 413 | `payload_too_large` |
| 422 | `invalid_request` |
| 429 | `rate_limited` |
| 500 | `internal_error` |
| 503 | `unavailable` |
| 504 | `timeout` |

### Error body

```json theme={null}
{
  "detail": "Insufficient API credits",
  "code": "payment_required",
  "correlation_id": "enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21"
}
```

| Field | Description |
| - | - |
| `detail` | What went wrong. See [Error Response Format](#error-response-format). |
| `code` | Stable, for programs. When `detail` is an object with its own `code`, this is that value. Otherwise it follows the status. |
| `correlation_id` | Equals the `X-Correlation-ID` response header. Include it when reporting a problem. |
| `feedback` | A hint for reporting a problem through [`POST /feedback`](https://docs.sixtyfour.ai/guides/report-wrong-data). |

| Status | `code` |
| - | - |
| 400 | `bad_request` |
| 401 | `unauthenticated` |
| 402 | `payment_required` |
| 403 | `forbidden` |
| 404 | `not_found` |
| 405 | `method_not_allowed` |
| 409 | `conflict` |
| 410 | `gone` |
| 413 | `payload_too_large` |
| 422 | `invalid_request` |
| 429 | `rate_limited` |
| 500 | `internal_error` |
| 502 | `bad_gateway` |
| 503 | `unavailable` |
| 504 | `timeout` |

Examples on this page show only `detail`.

### Field errors

Request validation errors (`422`) carry a `detail` array with one entry per invalid field. `loc` is the path to the field. `ctx`, when present, holds the rule the value broke, such as `{"max_length": 100000}` for a `research_plan` that is too long.

```json theme={null}
{
  "detail": [
    {
      "type": "missing",
      "loc": ["body", "lead_info"],
      "msg": "Field required",
      "input": {"struct": {"title": "Current job title"}}
    }
  ]
}
```

### 400 Bad Request

Causes:

* Missing required fields in request body
* Invalid field types or formats
* Malformed JSON payload
* Empty or invalid lead/company data
* Company Intelligence with `"tier": "scout"`. Scout is a People Intelligence tier
* A workflow definition that fails validation, such as one with no blocks, incompatible blocks, or broken edges. The response is `Workflow validation failed`, with one `validation_errors` entry per problem
* A workflow definition nested more than 64 levels deep, with `detail.code` `workflow_definition_too_deep`
* Sending `webhook_payload` to `/workflows/run` for a workflow whose source block is not `webhook`
* Triggering a `read_csv` workflow without a valid `specs_override.resource_handle_id` from `/storage/csv/upload`, or with a `handle_id` that belongs to a different organization
* `webhook_payload` is missing required columns from the `webhook` block's `input_schema`, or is malformed JSON
* `webhook_payload` rows with top-level keys that start with `_`: `Invalid input payload: Webhook input contains reserved top-level keys starting with '_' ...`
* Running a `webhook` workflow without `webhook_payload` when it has no saved sample input: `Webhook input is required but not provided`
* A `/storage/csv/upload` file with column names that start with `_`, other than `_row_id`: `Column names must not start with an underscore: ...`
* Invalid search exclusions: sending the deprecated `exclude_public_ids` in company mode (people-only) or alongside `exclude_entity_ids`, using a saved exclusion list whose entity type doesn't match the search mode or that is not yet `ready`, or sending exclusions on a cursor request, see [Search Exclusions](https://docs.sixtyfour.ai/api-reference/search/search-exclusions.md)
* A Bulk Intelligence `webhook_url` that is not `https://`. Async-job endpoints return `422` for the same URL
* A `webhook_url` query parameter on `POST /workflows/run`. Add an `outgoing_webhook` block instead
* An invalid cron expression or timezone on a schedule: `Invalid schedule, check the cron expression and timezone.`
* Invalid monitor requests. See [Monitors](#monitors)

Examples:

Company Intelligence with `"tier": "scout"`:

```json theme={null}
{
  "detail": "Unsupported enrichment tier 'scout'."
}
```

A workflow with no blocks:

```json theme={null}
{
  "detail": {
    "message": "Workflow validation failed",
    "validation_errors": [
      {
        "field": "blocks",
        "code": "EMPTY_BLOCKS",
        "message": "Workflow must have at least one block",
        "context": {"summary": "The workflow definition is malformed"},
        "blocking": true
      }
    ]
  }
}
```

Each save checks the schema and edges, block type compatibility, required block fields, and every column a block references against what its upstream blocks produce. Each entry in `validation_errors`:

| Field | Meaning |
| - | - |
| `field` | Path to the value, such as `blocks[1].specs.email_column`. Block indexes count along `edges` from the source block, `blocks[0]`, or follow request order when the edges are invalid. Use `context.block_id` to find the block. |
| `code` | Stable, such as `COLUMN_NOT_FOUND`, `MISSING_REQUIRED_FIELD`, `INVALID_FIELD_NAME`, `INVALID_SPECS`, `TYPE_INCOMPATIBLE` or `MULTIPLE_SOURCE_BLOCKS`. |
| `message` | What is wrong. |
| `blocking` | Always `true` on a `400`. |
| `context.block_id`, `context.block_name` | The block. `block_id` is your ID if it was a UUID, otherwise the one assigned. Absent when the finding concerns the whole graph. |
| `context.missing_columns`, `context.available_columns` | What you referenced and what exists at that point. At most 50 available names; `available_column_count` has the total when truncated. |
| `context.suggestion` | A hint for people, not programs. |
| `context.suggested_replacement` | A fragment to merge into the block's `specs`. |
| `context.summary` | The finding in one plain line. |

How to fix:

* Fix each field named in `detail` and resend
* For workflow runs, match the request body to the source block: `webhook_payload` for `webhook` workflows ([Incoming Webhooks](https://docs.sixtyfour.ai/api-reference/webhooks/incoming.md)) or `specs_override.resource_handle_id` for `read_csv` workflows ([Workflow Execution](https://docs.sixtyfour.ai/api-reference/workflows/workflows-execution.md)).

### 401 Unauthorized

Causes:

* Missing credentials
* Invalid, revoked, or expired API key
* Invalid or expired OAuth bearer token
* An API key sent as `Authorization: Bearer`

The `detail` text varies by endpoint; branch on the status or `code`.

| `detail` | Cause |
| - | - |
| `Unauthorized` or `Authentication required: provide Bearer token or X-API-Key header` | No credentials |
| `Unauthorized` or `Invalid API key` | An invalid, revoked, or expired API key |
| `Invalid bearer token` or `Invalid token` | An `Authorization: Bearer` value that is not an OAuth access token, such as an API key |
| `OAuth access token has expired` | The OAuth token is past its `expires_in` |
| `OAuth access token has been revoked` | The OAuth token was revoked |
| `OAuth client is disabled`, `OAuth client not found` | The OAuth client was disabled or deleted |
| `Invalid OAuth access token` | The token was altered or did not come from `POST /oauth/token` |

Example:

```json theme={null}
{
  "detail": "Unauthorized"
}
```

How to fix:

* Ensure the `x-api-key` header is included in every request, with no extra whitespace, or send an OAuth token as `Authorization: Bearer`. See [Authentication](https://docs.sixtyfour.ai/api-reference/authentication.md)
* Send API keys only in `x-api-key`; see [How the API picks a credential](https://docs.sixtyfour.ai/api-reference/authentication.md#how-the-api-picks-a-credential)
* Check that your API key hasn't been revoked or expired
* Request a new OAuth token before the old one expires
* Get a new API key from the [dashboard](https://app.sixtyfour.ai)

### 402 Payment Required

Causes:

* Your balance doesn't cover the request's estimated cost. See [Credit Costs](https://docs.sixtyfour.ai/guides/credits-and-pricing.md)
* Your organization has no active subscription
* Your team has reached its monthly spend limit, including when you create a monitor or change its tier

Examples:

```json theme={null}
{
  "detail": "Insufficient API credits"
}
```

```json theme={null}
{
  "detail": "This team has reached its monthly spend limit. Ask an organization admin to raise it."
}
```

When automatic top-ups are on and one has been requested, a workflow run or Bulk Intelligence start returns a `402` with `Retry-After: 30`. Retry after the delay; once the top-up is paid, the start goes through.

```json theme={null}
{
  "detail": "Insufficient API credits to start this run; a top-up has been requested."
}
```

If the balance stops covering a run after it is accepted, an async job ends `failed` with `error` set to `Insufficient API credits`, and a sync request returns `500`.

How to fix:

* Add credits or upgrade your plan in the [billing section](https://app.sixtyfour.ai/billing) before resubmitting
* Reduce the row count or use a cheaper tier to lower the estimated cost. See [Credit Costs](https://docs.sixtyfour.ai/guides/credits-and-pricing.md)
* For a team spend limit, ask an organization admin to raise it

Nothing is charged when a request returns 402.

### 403 Forbidden

Causes:

* Requesting a tier that is not enabled for your organization: `high`, `scout`, or `xhigh` (`micro`, `low`, and `medium` are available to every organization)
* Requesting a tier your organization has but your team is excluded from. The response is the same `403` an organization without the tier gets
* Calling `/v1/atlas/*` when Atlas is not enabled for your organization
* Calling any `/monitors` endpoint when Monitors are not enabled for your organization
* Creating or updating a monitor with the `5m` frequency or `micro` tier when they are not enabled for your organization
* Your organization's access to Sixtyfour has been locked

Examples:

```json theme={null}
{
  "detail": "High tier company enrichment is not enabled for this org. Contact sales to request access."
}
```

```json theme={null}
{
  "detail": "Scout tier lead enrichment is not enabled for this org. Contact sales to request access."
}
```

```json theme={null}
{
  "detail": "This tier is not enabled for your organization."
}
```

```json theme={null}
{
  "detail": "Monitors are not enabled for your organization."
}
```

```json theme={null}
{
  "detail": "This organization no longer has access to Sixtyfour. Contact your representative at Sixtyfour."
}
```

How to fix:

* Contact [support@sixtyfour.ai](mailto:support@sixtyfour.ai) to request access to a restricted tier or feature
* Use a tier your organization has access to, such as `low` or `medium`

### 409 Conflict and 428 Precondition Required (Workflow Edits)

An existing workflow content update requires `expected_revision`, copied from the latest workflow read's `edit_revision`. Missing it returns `428` with `detail.code: "workflow_revision_required"`. A stale revision returns `409` with `detail.code: "workflow_draft_conflict"`, `current_revision`, and the current workflow in `current_workflow`. Nothing from the stale update is saved.

Apply your changes to `current_workflow` and resend with `current_revision` as `expected_revision`. Resending the old definition with the new revision overwrites the other edits.

Updating a deleted workflow returns `404`. Changing the blocks of a locked workflow returns `409` (`Workflow is locked. Unlock it before changing its blocks.`); name and description changes still apply.

A run with `expected_revision` returns `409` if the revision changed (`workflow_draft_conflict`) or the workflow has a draft that failed validation (`workflow_draft_not_runnable`). No new run starts for either refusal.

### 503 Service Unavailable

Sixtyfour is briefly unavailable or at capacity. Requests refused before they run are not charged. Retry after the `Retry-After` header.

For `POST /workflows/run`, a `503` with code `workflow_input_unavailable` means the run's input could not be kept or read within the 15-second limit for preparing the run's input. No run was started and nothing was charged. Retry after `Retry-After` with the same body. If the message says saved rows failed their integrity check, replace the input rows or contact support. While saving input is only slow, the run still starts, as long as the input is kept within that limit.

```json theme={null}
{
  "detail": {
    "message": "Workflow input could not be stored. No run was started and nothing was charged; retry, with the same Idempotency-Key if you send one.",
    "code": "workflow_input_unavailable"
  },
  "code": "workflow_input_unavailable",
  "correlation_id": "enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21"
}
```

For `POST /workflows/cancel`, a `503` means the cancellation is not confirmed. Retry the cancel for the same `job_id` and poll [live status](https://docs.sixtyfour.ai/api-reference/workflows/workflows-execution.md#get-live-status) until the run ends. Do not start another run.

| `detail` | When | `Retry-After` |
| - | - | - |
| `Could not start this request right now. You were not charged. Retry shortly.` | The request could not be started | 5 |
| `Could not verify the API key right now. Retry shortly.` | The API key could not be checked | 5 |
| `Access could not be checked right now. Try again shortly.` | Your tier or team access could not be checked | 5 |
| `Our database is unavailable. Retry shortly.` | Sixtyfour's data was briefly out of reach, on any endpoint | 5 |
| `Enrichment is at capacity right now. Nothing was charged. Retry after the Retry-After header.` | A sync People Intelligence, Company Intelligence, or QA Agent request found no capacity | 30 |
| `Search is at capacity right now. Retry shortly.` | Search is at capacity | 30 |
| `Live status is temporarily unavailable. Retry after the Retry-After interval.` | `GET /workflows/runs/{run_id}/live_status` could not read the run's status. The run is unaffected | 5 |
| `Workflow results are temporarily unavailable. Please retry shortly.` | A workflow's results could not be read. The run is unaffected | 15 |
| `Some JSON results are still being saved. Retry shortly, or download the CSV now.`, or the same with `NDJSON` | A JSON or NDJSON link request for a step whose files are still saving | 60 |
| `History export capacity is temporarily unavailable.` or `History export timed out. Select fewer dates and retry later.` | `POST /monitors/{monitor_id}/history-export` | 15 |
| Starts with `Request capacity is temporarily unavailable.` | An endpoint with a burst budget is briefly unavailable | 15 |
| `detail.code` is `workflow_input_unavailable` | The run's input is briefly unavailable | 5 |
| `Email verification is temporarily unavailable. Retry shortly.` | `POST /verify-email` could not reach a verdict | None |

The `-async` endpoints never return the capacity `503`; their jobs wait. See [Async Jobs](https://docs.sixtyfour.ai/api-reference/legacy.md#statuses).

### Search

| Status | `detail` | Cause |
| - | - | - |
| 400 | `Invalid cursor.` | The `cursor` was altered or did not come from this search |
| 400 | `Cursor expired. Start a new search.` | The cursor was already used or has expired. Start again from the `search_id` |
| 400 | `Cursor requests must only include cursor. Omit ...` | A cursor request also sent other fields |
| 400 | `Cursor references an exclusion list that is no longer available. Start a new search.` | An exclusion list the search used was deleted |
| 400 | `Search is not completed (status: ...)` | Replaying a search, or building an exclusion list from it, before it finished |
| 400 | `max_results must be between 1 and ...` | `POST /search/export` with `max_results` out of range |
| 400 | `Lookalike tasks must be polled via GET /search/lookalike/{task_id}` | A lookalike `task_id` sent to `GET /search/status/{task_id}` |
| 400 | `Exclusion list limit (20) reached. Delete unused lists first.` | Your organization has the maximum number of exclusion lists |
| 400 | `name is required for this source type.` | Creating an exclusion list from a source other than a `search_id` without a `name` |
| 404 | Starts with `Search not found` | Replaying, exporting or building an exclusion list from a `search_id` that does not exist or that you cannot see. See [Replay a saved search](https://docs.sixtyfour.ai/api-reference/search/search-results.md#replay-a-saved-search) |
| 404 | `Task not found` | A `task_id` from another organization or team. An unknown `task_id` returns the object shown in [Object](#object) |
| 409 | `Cursor is being processed. Try again.` | Another request is using the same cursor. Retry it after that request finishes |
| 409 | `Export already in progress. Poll /search/status/...` | An export of the same search is still running |
| 409 | Starts with `Saved lookalike`, or says the seed profiles are gone | The lookalike search cannot be replayed. Run it again |
| 500 | `Could not save this search.` | `POST /search/start-deep-search` could not save the search. A `search_id` that is not a UUID or was already used returns this on every retry; send a new UUID |
| 503 | `Search is at capacity. Retry shortly.`, `Query embedding is temporarily unavailable. Retry shortly.`, `Exclusion lists are temporarily unavailable. Retry shortly.` or `Canonical entity IDs are temporarily unavailable. Retry shortly.` | Search cannot serve this request right now. There is no `Retry-After`; retry with backoff |
| 503 | `Lookalike results are temporarily unavailable` | `GET /search/lookalike/{task_id}` could not load results. There is no `Retry-After`; retry after a few seconds |
| 504 | `Seed identity resolution timed out; retry the request.` | `POST /search/lookalike` could not resolve the seed profiles in time. No search started, so retrying is safe |

### Workflow result download retries

`GET /workflows/runs/{run_id}/results/download-links` returns `429` or `503` with `Retry-After`. Wait that long and send the same request. Neither response affects the run or its results, so do not start a new run to recover a download. See [Rate Limits](https://docs.sixtyfour.ai/api-reference/rate-limits.md#workflows).

### Skills

| Status | `detail` | Cause |
| - | - | - |
| 403 | `Team skills are not enabled for your organization.` | Team skills are not enabled for your organization |
| 403 | `Only a team owner or an organization admin can change the team's skills` | The caller can read the team's skills but not change them |
| 403 | `Team skills are managed by a person: sign in, or use an API key a team member created` | The API key has no creator on record |
| 404 | `The team has no skill with this name` | `GET /skills/{name}` for a name the team doesn't have |
| 404 | `Team not found` | The caller's team no longer exists, or the caller can't see it |
| 409 | `The team already has a skill named employment-history. Send its version to replace it.` | A `PUT` without `version` for a name the team already has |
| 409 | `The team's skill employment-history changed or was deleted since that version. Read it again.` | The `version` is not the skill's current one |
| 422 | `A skill's name is lowercase letters and digits joined by hyphens, at most 64 characters` | The name in the path is not valid |
| 422 | `The skill's name: field must be the name in the address. Make the two names match.` | The frontmatter `name` differs from the name in the path |
| 422 | `version is not a version a read returned` | The `version` is not in the format a read returns |
| 422 | `The team's skills would take … tokens of every run's prompt, past the limit of 2000. …` | The team's listing would pass its limit |
| 422 | Names the field and what to change | The Markdown is not one valid skill, such as an unknown frontmatter field or a link to a file beside it |
| 422 | [Field errors](#field-errors) | A field is too long or the wrong type |
| 400 | `1 of the skills named is not listed for this run. Skills it may use: …` | A run attaches a skill the team doesn't have |
| 400 | `The attached skills take … tokens together, past the limit of 25000. …` | A run attaches more than its limit |
| 400 | `Skills are not enabled for this organization, so a run cannot attach any.` | A run attaches skills while team skills are not enabled |
| 400 | `skills is taken only by the xhigh tier, scout with graph, and the high tier.` | A run on another tier attaches skills |

Nothing is saved or started for any of these.

### Connections

| Status | `detail` | Cause |
| - | - | - |
| 403 | `Connected sources are not enabled for your organization.` | Connections are not enabled for your organization |
| 403 | `Only a team owner or an organization admin can change the team's connections` | The caller can read the team's connections but not change them |
| 404 | `No connection by that name in this team.` | The team has no connection with this name |
| 404 | `Team not found` | The caller's team no longer exists, or the caller can't see it |
| 400 | Starts with the field, such as `base_url: must start with https://.` | A field breaks a connection rule; the message says what to change |
| 400 | `name: this team already has a connection called crm. Edit it, or choose another name.` | `create_only` with a name the team already has |
| 400 | `This team already has 10 API connections. Remove one before adding another.` | The team has its limit of connections |
| 400 | `secret: required to connect an API.` | Creating a connection without `secret` |
| 400 | `secret: enter it again to change the base URL's host or the sign-in.` | A change of host or sign-in without `secret` |
| 400 | `secret: it was replaced during this edit; enter it again, or edit again.` | Someone replaced the secret during an edit that keeps it |
| 400 | `Your active team changed while this was open. Try again from the team that should own it.` | `team_id` is not the caller's team |
| 400 | `connections: 1 of the names given is not one of this team's connections. Its connections: …` | A run names a connection the team doesn't have |
| 400 | `connections: list each connection once.` | A run names a connection twice |
| 400 | `connections: connected sources are not enabled for this organization.` | A run names connections while they are not enabled |
| 400 | `connections is taken only by the xhigh tier, scout with graph, and the high tier.` | A run on another tier names connections |
| 422 | [Field errors](#field-errors) | A field is too long or the wrong type |

Nothing is saved, sent or started for any of these. Error responses never repeat the secret.

### LinkedIn monitor validation and access

| Status | Cause |
| - | - |
| 422 | `POST /monitors/linkedin` with an invalid or company URL, no or unsupported fields, unknown fields, extra columns, a duplicate profile, or a frequency outside 7 to 365 days |
| 400 | An update with a frequency outside 7 to 365 days |
| 422 | An update that changes the selected fields or sends a tier |
| 403 | LinkedIn monitors are not enabled for your organization; listings omit them |
| 409 | An idempotency key reused with different creation content |

### Verify Phone column mappings

Rows with a phone but no value in the configured `name_column` skip verification without failing the batch. They return `Missing Name` in `phone_warnings` and `MissingRequiredInput` details in `phone_errors`.

The name mapping must match the input column. For example, data containing `fullName` requires `name_column: "fullName"`. See [Verify Phone](https://docs.sixtyfour.ai/guides/building-workflows.md#intelligence) to update a saved mapping.

A missing phone column fails the block; a blank phone value skips the row.

### Error Response Format

`detail` is a string, a list of field errors, or an object.

### Object

Workflow errors carry an object with a `code` and a `message`:

```json theme={null}
{
  "detail": {
    "code": "workflow_revision_required",
    "message": "Read the workflow and supply its edit_revision as expected_revision."
  }
}
```

Other objects:

| Response | `detail` |
| - | - |
| `404` from `GET /job-status/{job_id}` | `{"message": "Job not found", "job_id": "..."}` |
| `404` from `GET /verify-age/{task_id}` | `{"message": "Job not found", "task_id": "..."}` |
| `404` from `GET /search/status/{task_id}` or `GET /search/lookalike/{task_id}` for an unknown `task_id` | `{"message": "Task not found", "task_id": "..."}` |
| `400` for an invalid workflow definition | `{"message": "Workflow validation failed", "validation_errors": [...]}` |
| Errors from `POST /search/filter-field-values` | `{"code": "...", "detail": "...", "retryable": true}`. See [Filter field values errors](#filter-field-values-errors) |

### Monitors

These requests return `400`. See [Monitor Endpoints](https://docs.sixtyfour.ai/api-reference/monitors/monitors-endpoints.md).

| Request | Cause |
| - | - |
| Create or update | A `frequency` outside `1h`–`365d`, a `tier` other than `low`, `medium`, or `high`, a `subject_type` other than `company` or `lead`, an empty `struct`, a column used as both a key column and a watched field, a row with no value in any key column, two rows with the same key values, or a non-public `webhook_url` |
| [Create from a file](https://docs.sixtyfour.ai/api-reference/monitors/monitors-endpoints.md#create-monitor-from-a-file) | A file that is not `.csv`, `.json`, `.jsonl`, or `.ndjson`, is larger than 100 MB, has no rows or more than 100,000 rows, or cannot be parsed; a `config` that is not valid JSON, contains an unknown field, has an empty or invalid `webhook_event_types` list, or names a `key_columns` entry missing from the file |
| `handle_id` | A file that cannot be parsed, or has no rows or more than 100,000 rows |
| [List rows](https://docs.sixtyfour.ai/api-reference/monitors/monitors-endpoints.md#list-rows), `GET /monitors/{monitor_id}/runs` | A `cursor` that did not come from a previous `next_cursor` |
| `GET /monitors` | A `cursor` that is not an ISO timestamp with a timezone |
| Update | The new schedule cannot be applied: `Could not apply the new schedule.` Retry the update |
| History export | An end date before the start date, or a range with no snapshots (`No snapshots in this date range.`) |

Two rows with the same key values:

```json theme={null}
{
  "detail": "Rows 0 and 3 have the same identity values (Acme Robotics, acmerobotics.com). Add a column that tells them apart, or remove the duplicate."
}
```

### Filter field values errors

`POST /search/filter-field-values` puts a `code` in `detail`:

```json theme={null}
{
  "detail": {
    "code": "aggregation_failed",
    "detail": "Failed to fetch field values."
  }
}
```

| Status | `code` | Meaning |
| - | - | - |
| 400 | `invalid_request`, `unsupported_mode`, `invalid_scoped_filters`, `unsupported_field`, `top_values_not_supported` | The request is invalid; fix it |
| 500 | `aggregation_failed` | The values could not be fetched; retry with backoff |

### OAuth token errors

`POST /oauth/token` uses the OAuth format, with `error` and optional `error_description`, rather than either response above:

```json theme={null}
{"error": "invalid_grant", "error_description": "The authorization grant is invalid or expired"}
```

Do not apply the /v1 code list to token responses.


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