Skip to main content
POST
Start validation
This is step 4 of the upload and render workflow. Validation analyzes the source project and records the scene data required for rendering. Poll GET /jobs/{id} until data.status becomes validated or failed.External API v1 requires validation for each new job. If the job reports validated, proceed to rendering without calling this endpoint again.

Configuration defaults

Omit optional fields to let Renderjuice select the blend file and the scene saved as active.

Bundled add-ons

For a ZIP created by Blend Project Packer, bundledAddonPathsToUse selects add-ons embedded in the project archive. Values are exact addons.items[].bundled_path_in_pack strings from blend-project-pack.json.
  • Omit bundledAddonPathsToUse to validate every bundled add-on in the pack.
  • Send an empty array to validate none of them.
  • Send a path array to validate only those bundled add-ons.

Authorizations

Authorization
string
header
required

API key authentication. Format: Bearer RJ-XXX.... Get your API key from the Renderjuice dashboard.

Path Parameters

id
string<uuid>
required

Unique identifier (UUID) of the job Unique identifier of the job

Example:

"123e4567-e89b-12d3-a456-426614174000"

Body

application/json
validationConfig
object

Optional validation configuration. If not provided, default validation settings will be used.

Response

Validation started.