Quickstart
Turn structured data into an on-brand PNG in three steps: create an API key, find a
template id, and call POST /v1/render. Same data in → same pixels out, every time —
your workspace brand is applied automatically.
1. Create an API key
Mint a key in the app at Settings → API keys. The plaintext key is shown once at creation — copy it and store it in a secret manager. See API keys for scoping and rotation.
2. Find a template
Every render needs a templateId. Browse the catalog to get one and learn the
values it accepts:
curl -sS "https://api.lemtika.com/v1/catalog" \
-H "Authorization: Bearer $LEMTIKA_API_KEY"
Each item carries an id like tmpl_og_card. Pass it to GET /v1/catalog/{id} to
read the exact variables. Full walkthrough in Find a template.
3. Render
POST /v1/render returns the raw image bytes synchronously. Send the templateId,
the per-variable values, and an optional target size:
curl -sS -X POST "https://api.lemtika.com/v1/render" \
-H "Authorization: Bearer $LEMTIKA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"templateId": "tmpl_og_card",
"values": { "headline": "Launch day", "metric": "10k users" },
"target": "og"
}' \
-o render.png
The response is Content-Type: image/png — the file is written straight to
render.png. Each successful render deducts 1 credit.
What to read next
- Authentication — the
Authorizationheader and 401s. - Find a template — the
tmpl_→valueshop. - The target model —
square·portrait·story·landscape·og. - Errors — the shared error envelope.