A conference name badge on a lanyard: first name in huge type, photo, role, company, a QR code and a colour bar for the ticket type.
These are real renders from the API with the example values in the table below. Switch the size above: the same template lays itself out for all 6 sizes — send size or sizes with the request.
For ticketing platforms and organisers who print or send a badge per attendee. The ticket_type picks the colour of the bar at the foot (attendee takes your accent, speakers red, sponsors gold, staff black, press teal); without a photo the badge shows the initials, without a QR image it draws an empty scan frame. Long names shrink to fit and the rest of the text is cut with an ellipsis. Portrait frames hang the classic tall badge with the name across its width; wide frames turn it into a landscape card with the photo left and the QR right.
Every field is optional. Long text shrinks to fit instead of overflowing; an image field takes a public URL that we fetch on our side.
| Field | Type | Description | Example |
|---|---|---|---|
first_name |
text | First name, set in the largest type. default: First name | Maya |
last_name |
text | Last name, under the first name. | Chen |
role |
text | Job title or role, e.g. Staff Engineer. | Staff Engineer |
company |
text | Company or organisation. | Northwind Labs |
ticket_type |
text | Ticket type that colours the bottom bar: attendee, speaker, sponsor, staff or press. one of: attendee | speaker | sponsor | staff | press default: attendee | speaker |
event_name |
text | Name of the event in the header band. | Frontend Summit 2026 |
event_dates |
text | Dates and place of the event, e.g. June 12–14 · Lisbon. | June 12–14 · Lisbon |
qr |
image URL | QR code image (generate it in your system and pass its URL). Without one the badge shows an empty frame. | https://example.com/images/b03-qr.png |
photo |
image URL | Attendee photo for the circle; initials are shown when it is missing. | https://example.com/images/avatar-woman.jpg |
logo |
image URL | Event logo in the header band. | https://example.com/images/logo-northwind.png |
accent |
colour | Brand colour as hex, e.g. #6366f1. Drives buttons, highlights and the background glow. default: #7c3aed | #7c3aed |
theme |
dark | light | Colour scheme: dark or light. | — |
Use the slug as template. The response holds the URL of the finished PNG; ?wait=true keeps the connection open until it is ready.
curl -X POST "https://shareglint.com/v1/images?wait=true" \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "event-badge",
"modifications": {
"first_name": "Maya",
"last_name": "Chen",
"role": "Staff Engineer",
"company": "Northwind Labs",
"ticket_type": "speaker",
"event_name": "Frontend Summit 2026",
"event_dates": "June 12–14 · Lisbon",
"qr": "https://example.com/images/b03-qr.png",
"photo": "https://example.com/images/avatar-woman.jpg",
"logo": "https://example.com/images/logo-northwind.png"
}
}'
For static sites, Webflow, Shopify and no-code tools: put the fields in the query string and sign it with your signing secret. The first request renders the image, every later one is a redirect to the cached file. How to compute the signature.
<meta property="og:image" content="https://shareglint.com/i/acc_YOUR_ACCOUNT_ID/event-badge.png?company=Northwind%20Labs&event_dates=June%2012%E2%80%9314%20%C2%B7%20Lisbon&event_name=Frontend%20Summit%202026&first_name=Maya&last_name=Chen&role=Staff%20Engineer&ticket_type=speaker&s=YOUR_SIGNATURE">
accent and theme change per request. For anything more, copy the template into your account: you get an ordinary HTML template with the same fields that you can edit in the dashboard or through the API. If the slug is free on your account, the copy takes it — your integrations switch to your version without changing a line.
curl -X POST "https://shareglint.com/v1/templates/library/event-badge/copy" \
-H "Authorization: Bearer sk_live_YOUR_KEY"