Every customer who holds an event has one ticket to it, with a 10-character code like T7K2M9QXWD that the door scans. The code is theirs alone and stays the same across renewals, upgrades and a return after a gap. A guest someone bought a ticket for holds their own ticket and code, the same way (see Guests); a buyer who gave every ticket away holds none. Reading it needs a token (Authentication); the example uses the client from Your own front end.
On your Sherpo storefront this is already built in: the event’s card in the customer’s library opens their ticket with its QR code. The rest of this page is for your own front end.
Read a ticket
GET /v1/stores/{store}/products/{product}/ticket reads the customer’s ticket to an event, with read.
curl 'https://api.sherpo.io/customer/v1/stores/yourstore.sherpo.io/products/slug:seed-saving-workshop/ticket' \
--header 'Authorization: Bearer ctk_...'{
"product_id": "<event id>",
"ticket_code": "T7K2M9QXWD",
"status": "going",
"cancel_reason": null,
"canceled_at": null,
"tier": { "id": "<tier id>", "name": "In person", "rank": 2 },
"registered_at": "2026-10-02T09:14:00.000Z",
"check_ins": [
{ "session_id": "<session id>", "checked_in_at": "2026-11-07T18:04:00.000Z" }
]
}ticket_codeis what to put in the QR code, as it is: the door’s scanner reads the code alone, so a QR code with no link tells a passer-by nothing. Show the code under it too, for a door whose camera can’t read the screen. It’snullwhenever the ticket doesn’t let them in (statusispending,waitlistedorcanceled), and for a moment while agoingticket’s code is still being minted. For the second, say the code is on its way and read the ticket again shortly.statusisgoingwhile the ticket lets them in,pendingorwaitlistedwhile their request waits, andcanceledonce it doesn’t, withcancel_reason(refunded,revoked,expired,declined, orcanceledwhen the seller canceled the event) andcanceled_at.check_insnames each session the door let them in at, earliest first. The event’s sessions, with their place, are on the product. Keep the QR code scannable while a later session is to come, so the ticket still works then.
It answers not_found when the customer never held or requested the event, or no event has that id or slug.