Real-time API

POST a payload.
Get an image.

Put creative generation inside your own product. Send a template id and a JSON object of variables, and get back a hosted image, delivered to your storage, with a webhook when it is ready. The same engine that powers the editor renders the API, so output matches the preview exactly.

Integration patterns

POST /v1/render

curl https://api.connectwyze.com/v1/render \
  -H "Authorization: Bearer $KEY" \
  -H "Idempotency-Key: order_8412" \
  -d '{
       "template": "tpl_summer",
       "variables": { "price": "$29" },
       "sizes": ["1080x1080"]
     }'

200 { "url": "https://cdn.you.com/…" }

Webhooks and callbacks

Fire-and-forget renders that notify your system the moment a job finishes, so you never poll for status.

Idempotency keys

Retries are safe. The same key returns the existing result instead of rendering, or charging, twice.

Your storage, your URLs

Renders land in your own Cloudflare R2, AWS S3 or Google Cloud Storage. No vendor lock-in on the asset layer.

Preview and output parity

The API and the editor share one Chromium render path, so what you designed is exactly what the endpoint returns.

For the moment an image has to exist.

A seller boosts a listing, a user publishes a post, a campaign fires. The API generates the on-brand creative at that exact moment, without you running headless browsers, managing fonts, or fighting drift between preview and output. That undifferentiated work is ours.

In practice

A 'boost my listing' button that just works

An online marketplace adding a paid promotion feature.

1
Situation
When a seller paid to boost a listing, an on-brand ad had to exist immediately, but building a render pipeline in-house meant running headless browsers and managing fonts.
2
What they set up
They call the render API when a boost is purchased, receive a webhook when the image is ready, and deliver it to their own R2 bucket.
3
Result
Sellers get an instant, on-brand ad the moment they pay, and the marketplace opened a new revenue line without operating any rendering infrastructure.

We shipped the feature in a sprint instead of building a render farm.

Engineering lead, online marketplace

New revenue line

Without running render infra

Wire the render endpoint into your stack.

Tell us where creative needs to appear in your product. We will walk through the API, webhooks and storage delivery against your use case.

The rest of the platform

One template is only the start.

Templates

Design once. Every size, language, and variant follows.

Data Sources

Point at a feed. The creative stays in sync with it.

Workflows

Set the rules once. Renders trigger themselves.

Background Removal

Studio-clean cutouts and shadows, baked into the render.

Image Library

Every render, searchable, exportable, hosted.

POST a payload.Get an image.