Queue a batch of up to 200 renders from a table

One template x a table of rows, rendered asynchronously. Use this instead of looping /render/batch when the set is bigger than 10: the quota is checked for the WHOLE batch up front, rows go through the shared render queue, and the result is one archive. Poll /batch-tasks/{id} for progress and fetch /batch-tasks/{id}/archive when it is done.

post/batch-tasks

Request

  • Base URL: https://rendry.io/api/v1
  • URL: https://rendry.io/api/v1/batch-tasks
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer
    • HTTP bearer

Headers

X-Rendry-Accountstring

Browser/OAuth current member account selector. API keys/embed credentials are bound to their persisted account and reject another account. Omitting this header selects the browser actor personal account.

Request body

preset_idstring required
tablestring required

CSV or TSV with a header row; up to 200 data rows

mappingobject

column -> template variable; omit to use the mapping from /batch-tasks/preview

rowsobject

Row sources for the WHOLE run — the arrays a repeat group or a table's rows_key consumes. A pasted cell is a string, so arrays travel here and not in the table; for a different basket per file, loop over render_image

format'png' | 'jpeg' | 'webp'
qualityinteger
max_widthinteger

Response

Queued. The rows render in the background; poll status_url.

task_idstring required
rows_totalinteger required

Data rows in the table

enqueuedinteger required

Rows that reached the render queue; the rest are reported as failed rows in the status

status_urlstring required

Path of GET /batch-tasks/{id}, relative to the API origin

Changes

No recorded changes to this operation across all 1 revision of this API.