Submit a durable render job

The same renders as the synchronous endpoints - kind is one of screenshot, pdf, qr, image, clip, site_preview, document or bundle and request is that endpoint's body (an image job names its template inside request) - accepted with 202 and run by a worker. Poll the job, or cancel it, then collect the result while it is hosted: 24 hours, private, through a signed link valid for 15 minutes. A process restart after the 202 never loses the job.

Send Idempotency-Key on every submission. The same key with the same request returns the existing job with 200; the same key with a different request is a 409 idempotency_conflict. external_id is your own reference, up to 120 characters.

Billing: the most the job can count is reserved on your billing account when it is accepted - in the same step, so a job you were told about always holds its reservation, and a refusal leaves no job. The one reservation is kept across retries of the job and committed, with what the job produced, when it succeeds; a site preview reserves the 60 second limit and commits its real length. A job that fails, is cancelled while queued, or is cancelled while running without a usable output, counts nothing. The job's usage says what it holds: {"meter", "reserved", "committed"}.

Capacity: an account may have 1,000 unfinished jobs (queued, running or being cancelled); a job past that is 429 queue_full and is not created. A job that uses the browser runs in one of the account's 2 browser slots, shared with its synchronous renders; while both are busy it waits in the queue rather than being refused.