Batch Jobs
Submit up to 1,000 render jobs in a single API request and track them as a group
A batch lets you submit up to 1,000 render jobs in oneDocumentation Index
Fetch the complete documentation index at: https://www.nexrender.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
POST /batches request. Each job in the batch follows the same schema as a single job. The API returns a batchId you can use to track progress and cancel the whole group at once.
Batches support partial success - if some jobs fail validation, the rest still proceed. The response tells you exactly which succeeded and which failed, with per-job error details.
Submit a Batch
jobs includes an index that maps back to its position in the original request array, so you can correlate results even when some fail.
Batch Creation Response
| Field | Type | Description |
|---|---|---|
batchId | string | Unique identifier for this batch |
status | string | "created" if all jobs succeeded, "partial" if some failed, "error" if all failed |
totalJobs | integer | Total number of jobs in the request |
successCount | integer | Number of successfully created jobs |
jobs | array | Details for each successfully created job |
errors | array | Details for each failed job (only present when status is "partial" or "error") |
Partial Success Example
If a job fails validation, its entry appears inerrors with an index matching its position in the original request. Successfully created jobs proceed normally.
Check Batch Status
PollGET /batches/:batchId to see aggregate progress across all jobs in the batch.
Batch Status Values
| Status | Meaning |
|---|---|
processing | At least one job is still running or queued |
finished | All jobs have completed (some may have errored) |
error | All jobs failed |
Batch Stats Fields
| Field | Description |
|---|---|
total | Total jobs in the batch |
finished | Jobs that completed successfully |
error | Jobs that failed |
pending | Jobs still queued or rendering |
Cancel a Batch
Cancel all remaining jobs in a batch with a single call. Jobs that have already finished are not affected.Cancellation Response Status Values
| Status | Meaning |
|---|---|
cancelled | Every cancellable job was cancelled |
partial | Some jobs were cancelled, others were already in a terminal state |
unchanged | No jobs were in a cancellable state |
When to Use Batches
- Rendering personalised videos for a large user list (event invites, product variants, certificates)
- Processing a bulk export where you want to submit all jobs upfront and track completion as a group
- Any workflow that needs atomic cancellation of many jobs at once
Rendering Basics
Nested Jobs
Authorizations
Bearer token authentication using API tokens for team-based access control.
You can generate your own API token at: https://app.nexrender.com/settings/api-tokens
Body
Configuration for creating a batch of render jobs in a single request (1 to 1000 jobs)
Array of job configurations to create as a batch. Each item follows the same schema as a single job creation request.
1 - 1000 elementsResponse
Batch created successfully. Check 'status' field: 'created' means all jobs succeeded, 'partial' means some failed (see 'errors' array).
Response after creating a batch of jobs, including per-job results and any errors
Unique batch identifier in ULID format for tracking the entire batch
'created' if all jobs succeeded, 'partial' if some failed, 'error' if all failed
created, partial, error Total number of jobs in the batch request
Number of successfully created jobs
Array of successfully created job details
Array of errors for failed jobs (only present when status is 'partial' or 'error')

