Skip to main content
GET
Get job details

Job Status Lifecycle

Poll a Single Job

Fetch the current state of a job at any time with GET /jobs/:id.

List Jobs

Use GET /jobs to fetch multiple jobs at once, with optional filters for status, date range, and sort order.

Query Parameters

Rather than polling, configure a webhook on the job to receive a notification the moment rendering completes or fails.
Nexrender will POST the full job payload to your endpoint when the job reaches a terminal state.
Your webhook endpoint must return a 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 OK immediately 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

Authorization
string
header
required

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

id
string
required

Unique job identifier

Response

Successfully retrieved job details

Render job with current status, progress, and detailed statistics

id
string

Unique job identifier used for tracking and API operations

templateId
string | null

Reference to the template used for this job (null if template was not used)

status
string

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.

progress
number<float>

Render progress as a percentage (0.0 to 100.0)

stats
object

Detailed timing and metadata statistics for the job

outputUrl
string | null

URL to the rendered content