Skip to main content

Legacy errors

Unversioned routes and replaced legacy routes keep their existing error formats. See Current APIs and Legacy.
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.

Error body

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.

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":
A workflow with no blocks:
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: 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. Example:
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:
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.
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:
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

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.
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. The -async endpoints never return the capacity 503; their jobs wait. See Async Jobs.

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.

Skills

Nothing is saved or started for any of these.

Connections

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

LinkedIn monitor validation and access

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.

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:
Other objects:

Monitors

These requests return 400. See Monitor Endpoints. Two rows with the same key values:

Filter field values errors

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

OAuth token errors

POST /oauth/token uses the OAuth format, with error and optional error_description, rather than either response above:
Do not apply the /v1 code list to token responses.