Event graphics follow a pattern: one design, dozens or thousands of copies with different names. A conference needs a card per speaker in three social sizes, a badge and a ticket per attendee, an "I'm attending" card people post themselves, and an agenda image for each track. With Shareglint you keep each design as a template and feed it your speaker sheet or registration export — one request per graphic, or one batch per list — and get back images and one-page PDFs. Six event templates are built in: speaker-card, attending-event, event-badge, event-ticket, event-agenda and webinar.
The templates and what they take
| Template | Fields | Typical use |
|---|---|---|
speaker-card |
title, name, role, event, label, date, photo | "Meet our speakers" posts |
attending-event |
name, role, title, company, event_name, date, location, booth, photo, event_logo | Cards attendees and sponsors share |
event-badge |
first_name, last_name, role, company, ticket_type, event_name, event_dates, qr, photo, logo | Printed name badges |
event-ticket |
title, admit, date, time, venue, city, section, seat, gate | Tickets in emails and wallets |
event-agenda |
title, items, date, venue, logo | Day or track schedules |
webinar |
title, label, date, time, timezone, host_1, host_2, avatar_1, avatar_2 | Online sessions |
Every built-in template renders in every size preset (og 1200×630, square 1080×1080, portrait 1080×1350, story 1080×1920, pinterest 1000×1500, youtube 1280×720) and takes accent (your brand colour) and theme (light or dark). That is the main time saver for social: one request with "sizes": ["og", "square", "story"] returns the LinkedIn/X card, the Instagram post and the story of the same speaker. The template gallery shows each one rendered.
Speaker announcements from the speaker sheet
Most events already keep speakers in a spreadsheet. Name the columns after the fields (name, role, title, photo, date) and send the sheet:
curl -X POST "https://shareglint.com/v1/batches" \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"template": "speaker-card",
"sizes": ["og", "square", "story"],
"csv_url": "https://docs.google.com/spreadsheets/d/…/edit?usp=sharing"
}'
Each row × size is one image. A filename column (anna-kowalska) names the files in the ZIP; event and label can be the same on every row or left to the template's defaults. When a speaker changes their title, edit the cell and run the batch again — only that speaker's images are rendered anew, the rest come back free. Rows per batch by plan: Free 50, Starter 500, Pro 1,000, Scale 2,000, Business 5,000. The dashboard's Bulk page does the same from an uploaded CSV, with a free preview of the first rows.
"I'm attending" cards that attendees post
The cards people share themselves spread an event further than its own account. Give each registrant a link to their card in the confirmation email:
- Signed URL — computed in your registration code from your account id and signing secret, with the attendee's
name,roleandcompanyin the query string. It renders the first time it is opened; nothing is rendered for people who never look. The personalized email images page shows the signing code and how to put the URL into a mailing tool. - Batch — render the whole list before the email goes out and store each URL with the registration.
Point the card's og:image at the same URL on a "share your ticket" page and the post previews correctly on LinkedIn and X.
Badges and tickets to print
For print, the output is a one-page vector PDF: "format": "pdf" gives a page exactly the template's size at 96 px per inch, text sharp at any zoom. Copy event-badge and set it to your badge size — 4×3 inches is 384×288 px, an A6 badge 397×559 px — then render the attendee export as one batch with format: pdf and a filename per attendee. The qr field takes the URL of a QR image from your ticketing system or a QR library such as node-qrcode or Python's qrcode, saved somewhere public; we lay it out, we do not generate it.
Two honest limits: each PDF is one badge (one page), so impositioning several badges onto an A4 sheet is your print shop's or your PDF tool's job; and the fonts are the families installed on our renderer (GET /v1/fonts), with no font upload. The PDF generation API page covers the PDF details.
Agendas and session graphics
event-agenda takes a list of items and lays out a day or track. Generate one per track when the schedule is final, and again in seconds when a session moves — the same values return the same file for free, changed ones render anew. webinar covers online sessions with one or two hosts and a time zone, for a social post or an email header.
Letting an assistant do the busywork
Connected to the MCP server, an assistant such as Claude or ChatGPT can run the same jobs from a chat: "render a square speaker card for each row of this sheet and give me the ZIP", or "make an agenda image for track B with these six sessions". It uses the same templates, account and quota.
Cost
One render per image and size; PDFs count the same. A conference with 40 speakers in three sizes is 120 renders; 1,500 printed badges are 1,500. The Free plan's 100 renders a month carry a watermark — for designing, not for the event. Starter is $9 a month for 2,000 renders, and a one-off pack of 1,000 for $8 covers the week of the event without changing plan (pricing).
Where other tools fit better
Template platforms such as Bannerbear, Placid and Canva's bulk create come with drag-and-drop editors and many more ready designs; if your marketing team designs every graphic visually, they are worth a look — see the Bannerbear comparison. We are the cheaper and more developer-shaped option when the designs are few, the data comes from your systems, and you want images and PDFs over one API.
