Verify webhook signatures
Each webhook carries an X-MGW-Signature header: HMAC-SHA256 of the raw body using your per-account secret. Recompute it on your side and compare in constant time before trusting the payload.
Guide
8 min readHow to Automate Mockup Generation with the API
When you're generating mockups for every SKU or design drop, the editor isn't the bottleneck — the manual steps are. Here's how to wire mockup rendering into your own pipeline over the API.
- 1
Create an API key
Generate a named, revocable API key on the API Keys page. Authenticate every request with an Authorization: Bearer header.
- 2
Render synchronously for instant results
POST to /api/v1/renders with a template id and a design (file, design_url, or stored asset id). The finished image returns in about a second.
- 3
Render asynchronously with webhooks
For heavier jobs, POST to /api/v1/render-jobs with a webhook_url. The render runs server-side and POSTs an HMAC-SHA256-signed payload on completion — no polling.
- 4
Generate variants in bulk
Submit a bulk job describing designs × templates × colors. It renders the whole matrix server-side, can be stopped anytime, and returns a zip — billing only for renders produced.
Reference designs without re-uploading
Upload reusable artwork once to your design library and reference it by asset id in every render. Repeated jobs never re-transfer the bytes, which keeps high-volume pipelines fast.
FAQ
Common questions
1.Is there an interactive API reference?+
Yes — /api/docs serves a live OpenAPI reference with try-it-out for every endpoint.
2.Do failed renders cost credits?+
No. Failed renders are never billed, and stopping a bulk job bills only the renders that completed.
Ready to ship better product visuals?
Free plan, no credit card, no watermarks — your first mockup in about a minute.
Start generating freeFree plan · no credit card · no watermarks
Photoshop-fidelity engineAPI with webhooksRenders never expire