Run a Playbook Against Uploaded Files
Run a playbook against one or more uploaded files and receive structured check results.
Requires a user-scoped API key (u:gcai_...). Files referenced by file_ids must belong to the caller and be in ready status. Poll GET /files/{id} until extraction completes. The playbook must be in completed status.
Set wait=0 or Prefer: wait=0 to enqueue the run and return immediately with a pending job envelope. Otherwise the endpoint waits up to the effective wait window before returning. Poll GET /jobs/{id} for the result if the job is not yet complete.
Documentation Index
Fetch the complete documentation index at: https://docs.gc.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
API key for authentication. Format: gcai_xxxxxxxxx
Create API keys in the GC AI app under Settings → API.
Headers
Optional RFC 7240 wait preference, for example wait=0. If both this header and the wait query parameter are supplied, they must match.
"wait=0"
Path Parameters
Playbook ID from GET /playbooks.
Query Parameters
Optional long-poll wait time in seconds. Use 0 for fire-and-forget behavior. If both wait and Prefer: wait=... are supplied, they must match. Values above 90 are clamped.
x >= 00
Body
IDs of uploaded files to review. Files must be in ready status. At least one file is required.
1Whose perspective the review takes. third-party reviews a counterparty document (default); first-party reviews your own.
first-party, third-party Name of the party the review represents (default: "our company").
Optional subset of check IDs to evaluate. Omit to run every check in the playbook.
1Response
Job completed within the effective wait window
Async job identifier
Stable job kind for this endpoint
playbooks/run Current job status
pending, running, succeeded, failed, canceled Playbook review payload when the job has succeeded
Failure payload when the job has failed
ISO 8601 creation timestamp
ISO 8601 completion timestamp, or null when not terminal