Playbooks
Run a playbook against uploaded files
Run a playbook against one or more uploaded files and receive structured check results.
<Note> This endpoint is asynchronous: it returns a job envelope, and the result is filled in once the job completes. See [Asynchronous Requests](https://docs.gc.ai/api-reference/concepts/async-jobs) for how waiting, polling, and the envelope work. </Note>Files referenced by file_ids must be accessible to the caller and in ready status. The playbook must be in completed status. Org-scoped keys can run org-visible playbooks against non-access-controlled files.
<Note> This is an inference endpoint and is [rate limited](https://docs.gc.ai/api-reference/concepts/rate-limits): 60 requests/minute per organization (20 per API key). Exceeding the limit returns `429` with a `Retry-After` header. </Note>post/playbooks/{id}/run
Request
- Base URLhttps://app.gc.ai/api/external/v1
- AuthAPI key in header Authorization
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
idstring uuid required
Playbook ID from GET /playbooks.
Query parameters
waitinteger nullable
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.
Headers
Preferstring
Optional RFC 7240 wait preference, for example wait=0. If both this header and the wait query parameter are supplied, they must match.
Example:wait=0
Request body
Response
Job completed within the effective wait window
Changes
No recorded changes to this operation across all 1 revision of this API.