On-demand render API

The missing render is ordered by your system, not a person.

On-demand render API

A PIM, ERP, store or partner portal orders a missing image and receives a status, an asset ID and a ready URL in return.

Order
a system on your side reports which image is missing.
Response
job status, asset ID and the URL of the finished file.
Cloud render
the job enters the queue with a priority, without your own render farm.
Publishing
the finished file lands in the gallery and in the target channel.

A complete catalog, not individual files

The API makes sure every catalog item has its approved shots - including items added after launch.

  • Illuminated glass display case with twelve compartments full of white products: cosmetics, an armchair, a lamp, a mixer, a faucet, a refrigerator, a sofa, a washing machine, a chest of drawers and a chair
    Approved renders of the entire catalogGaps are visible, and the missing shot is ordered by the system, not a person.

On-demand render API

One request orders a missing render.

A system on your side provides the SKU, shot, finish and channel profile. The response returns a job ID, and the finished file is reported to the callback URL you specify.

sku
Product identifier in your catalog.
view
Shot from the approved camera set.
finish
Finish from the material definitions.
profile
Channel profile: size, format and background of the output file.
callbackUrl
The address the finished render will be reported to.
Request
POST /api/renders
{
  "sku": "AR-410-CHROME",
  "view": "hero",
  "finish": "chrome",
  "profile": "product-page",
  "callbackUrl": "https://client.example/webhook"
}
Response
202 Accepted
{
  "render_job_id": 94821
}

You receive the job status and the finished file address at callbackUrl, or you poll by job ID.

From order to published file

Browse your current assets, order missing materials, update galleries automatically and share approved files.

  1. 01

    Management panel: A view of current assets and catalog gaps.

  2. 02

    Order: Request a missing render - from the panel or via the API.

  3. 03

    Cloud render: The job runs in the cloud on our side.

  4. 04

    Gallery update: Variant galleries refresh automatically after a change.

  5. 05

    Publishing and sharing: Files go to channels and partners, from a CDN.

A first concrete step

We are looking for companies to join the Renderomat pilot program.

We invite manufacturers, brands and distributors who want to be the first to implement automated packshot rendering for their catalog. After you apply, we will contact you to agree on the details together.

Apply for the pilot