Event & webinar banners

Generate event and webinar banners with an API

Spin up speaker cards, session banners and reminder images for every talk in a conference — same template, different name, date and topic, rendered in bulk.

Read the docs
100 renders / month free · no card · paid plans are never blocked
DevRender
14OCT
DevRender Summit
Lisbon · register now
A single template, rendered from your data

How it works

1

Design the banner

Lay out the event name, date, speaker and venue over your event branding.

2

Render per session

Loop over your schedule and render a card for each talk, speaker or reminder.

3

Share everywhere

Post them to social, embed in emails, or hand speakers their own promo cards.

One API call

curl https://api.mostlyrender.com/v1/renders \
  -H "Authorization: Bearer mr_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"templateId":"tpl_event_banner","modifications":{"event":"DevRender Summit","date":"14 Oct","city":"Lisbon"}}'

Questions

Can I generate one per speaker automatically?

Yes — loop over your schedule, send it as one batch request or run an n8n workflow, so every speaker and session gets its own card without manual design.

What sizes can I render?

Any. Templates are size-specific, so you can output square social posts, wide banners and story formats from the same speaker data by keeping one template per format.

Can I include speaker headshots?

Yes. Pass each headshot’s public image URL to an image layer and it’s placed into the design with your name, title and session text.

How do I render the whole programme in one go?

Use the batch endpoint: up to 50 renders per request, from one template or several, with each item metered separately and failures isolated to that item.

Can I put a registration QR code on the banner?

Yes. A QR layer takes the registration link as a modification, so each banner can carry its own code — trackable if you use a MostlyQR link.

What if the schedule changes after banners are shared?

Re-render with the new data. If you shared signed render URLs, a changed time or room means a new URL; images you didn’t change keep serving from cache.

Do I need a designer for every event?

Only once. Design the template in the editor, name the layers you want to change, and every later event reuses it by sending new data.