Handling Errors - Sixtyfour AI Documentation

Every Sixtyfour API error returns an HTTP status code and a JSON body. POST /oauth/token is the exception: it uses the OAuth error format. Branch on code, not on the text of detail.

Error body

{
  "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.
`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`.

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.

Error Response Format

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

String

Most errors carry a string detail:

{
  "detail": "Insufficient API credits"
}

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.

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

Object

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

{
  "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

OAuth token errors

POST /oauth/token returns errors in the OAuth format, error and error_description, without detail, code or correlation_id:

{
  "error": "invalid_client",
  "error_description": "client_assertion aud must match OAuth issuer"
}

`error`	Status	Cause
`invalid_request`	400	The request is malformed: an unsupported `client_assertion_type`, or an assertion without integer `iat` and `exp` claims or without `jti`
`invalid_client`	401	The client is unknown, disabled, or deleted, or the assertion is malformed, not signed with `RS256` by a registered key, missing `kid`, has the wrong `iss`, `sub`, or `aud`, lasts more than 300 seconds, or is issued in the future
`invalid_grant`	400	The assertion has expired, or its `jti` was already used
`invalid_scope`	400	A scope other than `full_access`
`unsupported_grant_type`	400	A grant type other than `client_credentials`
`invalid_target`	400	A `resource` other than the Sixtyfour API, more than one `resource`, or an `audience` parameter

A 429 from POST /oauth/token uses the detail format with Retry-After. See Rate Limits.

HTTP Status Codes

Status Code	Meaning	Description
200	OK	Request succeeded
202	Accepted	Async job or monitor accepted; poll for the result
400	Bad Request	Invalid request body, missing required fields, unsupported tier, or malformed data
401	Unauthorized	Missing or invalid API key or OAuth token
402	Payment Required	Insufficient credits, no active subscription, or the team’s monthly spend limit is reached
403	Forbidden	Tier or feature not enabled for your organization or team, or organization access is locked
404	Not Found	Resource not found (e.g., job, workflow, run, monitor, or investigation ID), or it belongs to another team
409	Conflict	The resource is not in a state that allows the request, or an identical request is still being processed
413	Content Too Large	A file, workflow definition, or export is past its size limit
422	Validation Error	Invalid request parameters; see the `detail` array for field-level errors
428	Precondition Required	An existing workflow content update omitted `expected_revision`
429	Too Many Requests	Rate limit exceeded; retry after the `Retry-After` header. See Rate Limits
500	Internal Server Error	Server error; retry with backoff
502	Bad Gateway	An upstream source failed; retry after a brief wait
503	Service Unavailable	Temporarily unavailable or at capacity; retry after the `Retry-After` header. Requests rejected before execution are not charged
504	Gateway Timeout	A search request timed out; retry after a brief wait

Common Error Types

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
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

Examples: Company Intelligence with "tier": "scout":

{
  "detail": "Unsupported enrichment tier 'scout'."
}

A workflow with no blocks:

{
  "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) or specs_override.resource_handle_id for read_csv workflows (Workflow Execution).

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:

{
  "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
Send API keys only in x-api-key; see 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

402 Payment Required

Causes:

Your balance doesn’t cover the request’s estimated cost. See Credit Costs
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:

{
  "detail": "Insufficient API credits"
}

{
  "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.

{
  "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 before resubmitting
Reduce the row count or use a cheaper tier to lower the estimated cost. See Credit Costs
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:

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

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

{
  "detail": "This tier is not enabled for your organization."
}

{
  "detail": "Monitors are not enabled for your organization."
}

{
  "detail": "This organization no longer has access to Sixtyfour. Contact your representative at Sixtyfour."
}

How to fix:

Contact 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

404 Not Found

Causes:

Workflow ID does not exist or was deleted
Run or job ID does not exist, has expired, or is invalid
Resource does not belong to your organization
The workflow or run belongs to another team. API keys and OAuth clients see only their own team’s workflows and runs
Monitor or row ID does not exist, or the monitor belongs to another team
A monitor handle_id that does not exist or belongs to another team: Upload handle not found.
GET /monitors/for-run/{workflow_run_id}/{block_id} for a step that started no monitor: No monitor was started by that step.
GET /v1/atlas/investigations/{investigation_id}/report.pdf before a report was requested, or after the last build failed. Send POST /v1/atlas/investigations/{investigation_id}/report, with retry_failed: true after a failure. It is also 404 once nothing reportable is left in the investigation

Examples:

{
  "detail": "Workflow not found"
}

GET /job-status/{job_id} returns an object:

{
  "detail": {
    "message": "Job not found",
    "job_id": "3f8b2c1e-7a4d-4e9b-8c21-5d6f0a9b1e47"
  }
}

How to fix:

Verify the workflow ID using GET /workflows
Verify the job_id from your run response
Ensure you’re accessing resources created by your organization, with a key or OAuth client from the team that owns them

409 Conflict (Monitors)

Causes:

Requesting GET /monitors/{monitor_id}/runs/{run_id}/changes when the run is running or failed. Changes are available only for completed runs; check the status with List monitor runs.
Triggering a monitor that is cancelled or paused
Updating a cancelled monitor or switching one of its rows on or off
Reusing a monitor idempotency key with different creation settings or file contents
Triggering a monitor, or changing its frequency or is_active, while its status is starting or failed, before every row from an uploaded file is added
Sending a create request while an identical one, with the same idempotency key, is still being processed

Examples:

{
  "detail": "This monitor is not active."
}

{
  "detail": "This request is already being processed. Retry shortly."
}

How to fix:

For a paused monitor, resume it with POST /monitors/{monitor_id}/update and "is_active": true, then trigger it
For a monitor whose status is starting, wait until it is active. For one whose status is failed, send the same upload request again, with the same file and settings, to finish it
A cancelled monitor cannot be resumed or changed. Create a new monitor to start checks again
For an idempotency conflict, retry with the original creation payload, or use a new key for a new monitor
If the request is still being processed, retry after a few seconds with the same payload and key; it returns what the first attempt created

409 Conflict (Atlas)

POST /people-intelligence-async with exclusive_run: true on an existing investigation returns 409 while that investigation already has a run starting or running. Wait for the current run to finish, then retry. POST /v1/atlas/investigations/{investigation_id}/runs has no exclusive_run option.

{
  "detail": "This investigation is already running. Send guidance to its agent or stop it before deploying again"
}

Starting a run or requesting a report while the investigation is being deleted also returns 409: Atlas investigation is being deleted or investigation is being deleted.

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.

409 Conflict (Workflow Runs)

POST /workflows/create_workflow with an id already in use, and a run of a workflow with no valid saved definition, also return 409.

`detail`	Cause	How to fix
`A request with this Idempotency-Key is still starting. Retry shortly.`	A `POST /workflows/run` with the same `Idempotency-Key` is still starting. Carries `Retry-After: 1`	Retry with the same key after `Retry-After`; it returns the run the first request started
`{"message": "This workflow or run was deleted. Create a new id or use a new idempotency key.", "code": "workflow_input_owner_deleted"}`	The workflow ID or idempotency key belonged to a deleted workflow or run	Use a new workflow ID or idempotency key

413 Content Too Large

Causes:

A /storage/csv/upload file larger than 45 MB: Tabular files must be 45MB or less
A workflow definition past its size or block-count limit, with detail.code workflow_definition_too_large
A monitor handle_id file larger than the monitor upload limit: Uploaded file exceeds the monitor upload size limit.
A monitor history export that is too large: History export is too large. Select fewer dates. or Too many snapshots. Select a smaller date range.

Nothing is saved or started. Send a smaller file, definition, or date range.

422 Validation Error (Monitors)

POST /monitors/{monitor_id}/update returns 422 for any request containing struct, even null or the current definition, and applies nothing. To change watched fields, create a new monitor. POST /monitors and POST /monitors/{monitor_id}/update return 422, with a field-level detail array, when webhook_event_types is empty or names an unknown event. See Monitor Endpoints.

422 Validation Error (Workflows and Other Monitor Requests)

Causes:

A workflow name, description, block field, or spec value past its limit, or a block name that does not exist, with detail.code workflow_field_too_long and one validation_errors entry per value
Missing required fields in create/update requests
Unknown fields in monitor create, update, row-toggle, source, or history-export JSON requests, such as frequncy instead of frequency
Toggling a monitor row without the required JSON body {"is_active": false} or {"is_active": true}; the query parameter alone is not accepted
A monitor handle_id that is not a tabular upload: Use a tabular upload handle from /storage/csv/upload.
A cursor for GET /monitors/for-run/{run_id} that did not come from a previous response: Invalid monitor page cursor.

Example:

{
  "detail": {
    "message": "workflow_name is 250 characters; the limit is 200.",
    "code": "workflow_field_too_long",
    "validation_errors": [
      {
        "field": "workflow_name",
        "code": "too_long",
        "message": "workflow_name is 250 characters; the limit is 200.",
        "context": {"limit": 200, "length": 250},
        "blocking": true
      }
    ]
  }
}

How to fix:

Shorten each value named in validation_errors
Check block compatibility (e.g., webhook → company_enrichment)
See GET /workflows/blocks for block specs

429 Too Many Requests

A request went over a rate or concurrency limit and did not run. Retry after the Retry-After header. See Rate Limits.

500 Internal Server Error

Example:

{
  "detail": "Internal server error"
}

A sync People Intelligence, Company Intelligence, or QA Agent request also returns 500 when its job fails after it was accepted, for example when the balance no longer covers it or a micro request asks for more than 10 fields. The -async endpoints report the same failure as a failed job. Failed to fetch user organization from API key means the API key could not be checked. Retry the request. How to fix:

Retry the request with exponential backoff
If the error persists, contact support@sixtyfour.ai with the response’s correlation_id

502 Bad Gateway

Endpoint	`detail`	Fix
`POST /monitors/{monitor_id}/cancel`	`Monitor is cancelled, but its schedule could not be paused. Retry cancellation to finish cleanup.`	The monitor is cancelled and runs no more checks. Retry the cancel to finish; repeating it is safe
`POST /monitors/{monitor_id}/trigger`	`Could not start the run.`	Retry the trigger
`POST /monitors/{monitor_id}/update`	`3 of 120 rows did not take the update; the monitor is unchanged. Retry to apply it.`	The monitor keeps its old settings. Send the same update again

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.

{
  "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 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	—

The -async endpoints never return the capacity 503; their jobs wait. See Async Jobs.

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
404	`Task not found`	A `task_id` from another organization or team. An unknown `task_id` returns the object shown in 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

Filter field values errors

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

{
  "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

Monitors

These requests return 400. See Monitor Endpoints.

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	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, `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:

{
  "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."
}

Signed download URLs

A download_url from workflow results or webhooks, and the url from GET /search/download, needs an API key or OAuth token from the same organization.

Status	`detail`	Cause
401	`Invalid or expired download token`	The link is older than 15 minutes or was altered. Request a fresh link
403	`Access denied`	The credential belongs to another organization
422	`This file could not be made safe to open in a spreadsheet: ...`	The CSV could not be escaped. Retry with `spreadsheet_safe=false` to download the file exactly as stored

Downloads share an organization budget; see Rate Limits.

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.

Private runs

Status	`detail`	Cause
403	`Private runs aren't available for your organization yet`	Private runs are not enabled for your organization
403	`Your team doesn't allow private runs`	Your team’s settings turn private runs off
400	`Private runs need a signed-in user or an API key with a known creator`	The API key has no creator on record. Use a key created by a team member
400	`private on xhigh (or scout with graph) is only supported on the async endpoint: use /people-intelligence-async.`	`private` sent to the sync endpoint
400	`private applies only to a new investigation, so it can't be combined with investigation_id.`	`private` sent with `investigation_id`
409	`This dispatch_id was already used for a run with a different owner. Send a new dispatch_id.`	The `dispatch_id` belongs to another owner’s run

Lattice

Status	`detail`	Cause
403	`The knowledge graph is not enabled for your organization.`	Lattice is not enabled for your organization
409	`The knowledge graph is unavailable for your organization. Contact support.`	Organizations with customer-managed encryption need Sixtyfour to set up Lattice first
401	`Dashboard authentication required for Lattice`	Graphs open only in the Sixtyfour app; an API key can run a workflow that builds one
409	`Another team already has a graph with this name. Choose a different graph name.`	Graph names are shared across your organization’s teams

Webhook test events

Status	`detail`	Cause
422	`Unknown event; use GET /webhooks/test-events`	The `event` is not in the catalog
422	`url must use HTTPS`, or why the URL was refused	The `url` is not a public HTTPS address
409	`Organization has no active signing secret; no webhook sent`	`signing` is `required` and your organization has no active signing secret
503	`Test events are unavailable right now; no webhook sent` or `The signing secret could not be read; no webhook sent`	Retry the request

No webhook is sent for any of these.

Feedback

Status	`detail`	Cause
404	`No task with that id in your organization. Leave out task_id to send general feedback.`	The `task_id` or `dispatch_id` names no task Sixtyfour still keeps, or one of another organization, or someone else’s private run
404	`No workflow run with that id in your organization. Leave out workflow_row to send general feedback.`	The `workflow_row` run does not exist, or belongs to another organization or team
404	`Feedback not found`	`GET /feedback/{feedback_id}` for feedback your team cannot read, including a result that is private, deleted, or no longer shared
409	`This Idempotency-Key was already used for a different request; nothing was saved. Use a new key for new feedback.`	The same `Idempotency-Key` with a different request
503	`We could not check that task just now; nothing was saved. Retry with the same Idempotency-Key, or leave out task_id and name it in comment.`	The task could not be looked up for a moment. Carries `Retry-After`
503	`Your feedback was not saved. Retry with the same Idempotency-Key.`	The feedback could not be stored. Carries `Retry-After`

A request with no comment, rating or corrections, corrections without task_id, dispatch_id or workflow_row, more than one of those three, a field corrected twice, a source_url that is not http or https, text holding the NUL character, or more than 256 KB of JSON returns 422. Nothing is saved for any of these.

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	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	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–365 days
400	An update with a frequency outside 7–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

LinkedIn monitor check failures

A LinkedIn monitor accepts any valid profile URL. A profile Sixtyfour has no data for reports a row error event on each check:

`payload.reason`	Meaning
`linkedin_profile_not_found`	Sixtyfour has no data for this profile.
`linkedin_profile_deleted`	The matching profile is marked deleted.

A failed check keeps the previous baseline and reports no changes; the next scheduled check tries again. See LinkedIn Monitors. A LinkedIn check that fails because the balance is too low writes no error event. It sends monitor.execution.failed instead.

Common Troubleshooting Scenarios

Issue: Request times out

Research calls take up to 10 minutes. Set your client timeout to at least 15 minutes, or use the -async endpoints with polling or webhook_url. A sync request keeps running, and is charged, after your client disconnects; see Sync calls and retries.

Issue: Empty or incomplete results

Send more identifiers (name, company, LinkedIn URL) and specific struct descriptions; check confidence_score.

Issue: Workflow run stuck or not progressing

Check:

Are you polling GET /workflows/runs/{run_id}/live_status?
Is the overall_status still queued, running, or finalizing?

Solution:

Poll every 10 seconds or slower and honor Retry-After. See Status polling
Any overall_status other than queued, running and finalizing is final
Use overall_progress_percentage and blocks to see per-block progress
To stop a run: POST /workflows/cancel?job_id={job_id}
Check each block’s error_message. Cancel and rerun a run that stops progressing

Issue: Webhook signature verification fails or deliveries stop

Check:

Is your verifier using the raw request body bytes, not a re-serialized JSON parse?
During rotation, does it iterate every v1= segment (not only the last)?
Is your server clock within 5 minutes of UTC?
Are you using the plaintext secret (sk_whsec_<64 hex>), not the masked preview shown in the dashboard?

Solution:

Log the raw body, the Sixtyfour-Signature header, and the HMAC your server computes; compare against what we sent.
See Signing Secrets & Verification for the verification algorithm and reference code.
When your organization has a signing secret and Sixtyfour cannot sign a delivery, it sends nothing. Results stay available at GET /job-status/{task_id}.

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 to update a saved mapping. A missing phone column fails the block; a blank phone value skips the row.

Getting Help

If you’re experiencing issues not covered in this guide:

Check the endpoint’s page for its requirements; the quick start lists every area
Check status.sixtyfour.ai for incidents
Contact support at support@sixtyfour.ai
Include the following in your support request:
- The correlation_id from the response
- Request/response details (remove sensitive data)
- Error message
- Endpoint being called
- Approximate timestamp of the error

​Error body

​Error Response Format

​String

​Field errors

​Object

​OAuth token errors

​HTTP Status Codes

​Common Error Types

​400 Bad Request

​401 Unauthorized

​402 Payment Required

​403 Forbidden

​404 Not Found

​409 Conflict (Monitors)

​409 Conflict (Atlas)

​409 Conflict and 428 Precondition Required (Workflow Edits)

​409 Conflict (Workflow Runs)

​413 Content Too Large

​422 Validation Error (Monitors)

​422 Validation Error (Workflows and Other Monitor Requests)

​429 Too Many Requests

​500 Internal Server Error

​502 Bad Gateway

​503 Service Unavailable

​Search

​Filter field values errors

​Monitors

​Signed download URLs

​Workflow result download retries

​Private runs

​Lattice

​Webhook test events

​Feedback

​Skills

​Connections

​LinkedIn monitor validation and access

​LinkedIn monitor check failures

​Common Troubleshooting Scenarios

​Issue: Request times out

​Issue: Empty or incomplete results

​Issue: Workflow run stuck or not progressing

​Issue: Webhook signature verification fails or deliveries stop

​Verify Phone column mappings

​Getting Help

Error body

Error Response Format

String

Field errors

Object

OAuth token errors

HTTP Status Codes

Common Error Types

400 Bad Request

401 Unauthorized

402 Payment Required

403 Forbidden

404 Not Found

409 Conflict (Monitors)

409 Conflict (Atlas)

409 Conflict and 428 Precondition Required (Workflow Edits)

409 Conflict (Workflow Runs)

413 Content Too Large

422 Validation Error (Monitors)

422 Validation Error (Workflows and Other Monitor Requests)

429 Too Many Requests

500 Internal Server Error

502 Bad Gateway

503 Service Unavailable

Search

Filter field values errors

Monitors

Signed download URLs

Workflow result download retries

Private runs

Lattice

Webhook test events

Feedback

Skills

Connections

LinkedIn monitor validation and access

LinkedIn monitor check failures

Common Troubleshooting Scenarios

Issue: Request times out

Issue: Empty or incomplete results

Issue: Workflow run stuck or not progressing

Issue: Webhook signature verification fails or deliveries stop

Verify Phone column mappings

Getting Help