API Documentation

Everything you need to call the Visora render API directly, plus the no-code integrations if you'd rather not.

Authentication

Every request needs your API key as a Bearer token: Authorization: Bearer VISORA_LIVE_.... Find your key on your dashboard.

Render endpoint

POST /api/v1/render — the one endpoint that does everything.

curl -X POST https://api.visor-a.com/api/v1/render \
  -H "Authorization: Bearer VISORA_LIVE_..." \
  -H "Content-Type: application/json" \
  -d '{"template_id": "product-banner", "format": "png", "data": {"title": "Air Max 270", "price": "$150"}}'

Request body

• template_id — a preset ID from the template gallery, or your own custom template.
• format — png or jpeg.
• data — an object of variables filling in the template's blanks.

Response

200 OK with a JSON body: { success, render_time, cached, data: { url, width, height, format } }. Identical requests are served from cache — cached: true — instead of re-rendering.

Errors

400 (bad request), 401 (invalid API key), 404 (template not found), 429 (monthly quota exceeded), 500 (render failed).

Rate limits & quota

Your plan's monthly render quota and current usage are visible on your dashboard. Requests past the quota return 429 until it resets or you upgrade.

Webhooks

On Pro and Agency, set a webhook URL from your dashboard and Visora POSTs a render.completed event there on every render, signed with HMAC-SHA256 (X-Visora-Signature header) so you can verify it's really from Visora.

Integrations

• Make.com — a Render Image action for any scenario.
• WordPress — one-click connect plus a [visora_render] shortcode.
• Telegram bot — render templates with a /render command, right from chat.
• Browser extension — right-click selected text on any page to render it (in testing).