Tracking Render Jobs
Poll job status, list jobs with filters, and receive webhook callbacks when rendering completes
Job Status Lifecycle
Poll a Single Job
Fetch the current state of a job at any time withGET /jobs/:id.
List Jobs
UseGET /jobs to fetch multiple jobs at once, with optional filters for status, date range, and sort order.
Query Parameters
Webhooks (Recommended)
Rather than polling, configure a webhook on the job to receive a notification the moment rendering completes or fails.POST the full job payload to your endpoint when the job reaches a terminal state.
2xx response. Make it idempotent - Nexrender retries failed deliveries up to 3 times with exponential backoff.Webhook Retry Logic
If your server is unavailable or returns a non-2xx response, Nexrender retries delivery up to 3 times with exponential backoff. To maximise reliability:- Respond with
200 OKimmediately and process the payload asynchronously - Keep response time under 2 seconds to avoid timeout-triggered retries
- Log all incoming webhook payloads for auditability
API Reference
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
Path Parameters
Unique job identifier
Response
Successfully retrieved job details
Render job with current status, progress, and detailed statistics
Unique job identifier used for tracking and API operations
Reference to the template used for this job (null if template was not used)
Current job status (queued, render:dorender, finished, error, etc.). Manually cancelled jobs are normalized to manually_cancelled in v2 responses even though they are stored internally as error.
Render progress as a percentage (0.0 to 100.0)
Detailed timing and metadata statistics for the job
URL to the rendered content

