Skip to navigation

Cancel Verify Run

Beta

Cancel an in-progress verify run.

Only runs with a status of "PROCESSING" are cancelled. Cancelling a run that has already completed, failed, or been cancelled is a no-op that returns the run unchanged. A cancelled run never produces output.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

idstringRequired

The ID of the verify run to cancel.

Example: "vr_xK9mLPqRtN3vS8wF5hB2cQ"

Headers

x-extend-api-version"2026-02-09"OptionalDefaults to 2026-02-09

API version to use for the request. If you’re using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.

x-extend-workspace-idstringOptional

The workspace ID to target. Required when using an organization-scoped API key; optional for workspace-scoped keys (the key is already tied to a workspace). See Authentication for details on API key scopes.

Response

Verify run cancelled (or already in a terminal state)

objectenum

The type of object. Will always be "verify_run".

Allowed values:
idstring

A unique identifier for the verify run.

Example: "vr_xK9mLPqRtN3vS8wF5hB2cQ"

fileobject or null

The file that was verified. null once the input file has been deleted.

statusenum

The status of the verify run:

  • "PROCESSING" - The document is still being checked
  • "PROCESSED" - Verification completed successfully; read output
  • "FAILED" - Verification failed (see failureReason for details)
  • "CANCELLED" - The run was cancelled before it completed
Allowed values:
outputobject or null

The verification result.

Availability: Present when status is "PROCESSED". For a zero-retention run the result is delivered once, in the synchronous response or the first GET, and purged afterwards; it is purged in any case one hour after the run reaches a terminal status.

failureReasonstring or null

The reason for failure.

Availability: Present when status is "FAILED".

Possible values include:

  • FILE_TYPE_NOT_SUPPORTED
  • NO_APPLICABLE_SIGNALS
  • PARSE_FAILED
  • REQUEST_ABORTED
  • INTERNAL_ERROR

Note: Additional failure reasons may be added in the future. Your integration should handle unknown values gracefully.

failureMessagestring or null

A human-readable description of the failure.

Availability: Present when status is "FAILED".

metadatamap from strings to any or null

Any metadata that was provided when creating the verify run.

Availability: Present when metadata was provided during creation.

metricsobject or null

Metrics about the verification process.

Availability: Present when status is "PROCESSED".

configobject

The configuration that ran, with defaults applied: the engine, the concrete engineVersion that "latest" resolved to, and advancedOptions.requireParsing as it applied to this run.

usageobject or null

Usage credits consumed by this verify run. Always null in the current release: verify runs are not metered during the beta.

sourceenum
How the run was created.
Allowed values:
sourceIdstring or null

An identifier for the request that created the run. For API-created runs this is the request ID, the same value returned as requestId on errors, which you can quote to support.

createdAtstringformat: "date-time"

The time (in UTC) at which the object was created. Will follow the RFC 3339 format.

Example: "2024-03-21T16:45:00Z"

updatedAtstringformat: "date-time"

The time (in UTC) at which the object was last updated. Will follow the RFC 3339 format.

Example: "2024-03-21T16:45:00Z"

Errors

400
Bad Request Error
401
Unauthorized Error
402
Payment Required Error
403
Forbidden Error
404
Not Found Error
422
Unprocessable Entity Error
429
Too Many Requests Error
500
Internal Server Error