Fill a form from values or source documents
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Query parameters
How many seconds to hold the request open waiting for the run to finish.
Finishing inside the window returns 200 with the full run; running past it returns 202 with a statusUrl to poll. Send 0 to skip waiting entirely and always get the 202.
Request
The blank form to fill, given one of two ways.
{ "id": "…" }— a saved template fromPOST /v1/templates, or any file you own.{ "url": "…", "name"?: "…" }— fetched for this run only and purged with it.
Optional when action names a saved config that carries one — sending it inline still wins.
Free-form guidance for the drafting pass — which source document wins a conflict, how to format dates, which fields to leave blank.
What the produced PDF looks like. flattened (the default) bakes the values in so nothing can be changed; editable leaves the form fillable.
The source documents the field values are drafted from, up to 100. Send this or values, never both.
The field values to write, keyed by field name — deterministic, no drafting pass. Send this or files, never both.
Arbitrary JSON you attach to the run and get back on every read of it.
Use it to carry your own identifiers — an order number, a customer id — so a webhook or a polled run reconciles without a lookup table. Capped at 10 KB serialized.
Where to deliver this run’s events, given one of two ways.
{ "url": "…" }— a one-off https endpoint for this run only.{ "id": "whe_…" }— a saved endpoint fromPOST /v1/webhooks. Runs hold the reference, so pausing or re-pointing that endpoint applies to this run too.
Deliveries are at-least-once and signed — dedupe on eventId and verify against GET /v1/webhooks/jwks.json.
How long, in seconds, to keep this run and its files before purging them automatically.
The maximum is 604800 (7 days). The deadline comes back as expiresAt on every read of the run. Call POST /v1/runs/{id}/keep before then to clear the TTL and move the results into a space permanently.
E-signature runs are exempt — an envelope waits for its signers however long that takes.
Response
Where the run is in its life.
The last four are terminal.
Why the run failed. Present whenever status is failed, and only then.
code is the stable, snake_case reason (input_unavailable, parse_failed, …); message is the human-readable detail. Per-file and per-step failures are also reported in files[].error and, for a pipeline, steps[].error.
The completed form. Present once status is processed.
file is the filled PDF with a signed download link; fields reports the values that were written into it, keyed by field name.