---
title: "Event tickets"
description: "Show a customer their ticket to an event, with the code its QR code holds, whether it still lets them in, and the sessions it let them in at."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sherpo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Event tickets

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](/customer-api/checkout#guests)); a buyer who gave every ticket away holds none. Reading it needs a token ([Authentication](/customer-api/authentication)); the example uses the client from [Your own front end](/customer-api/self-hosted#a-minimal-client).

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`](/customer-api/reference/get-ticket) reads the customer's ticket to an event, with `read`.

```bash
curl 'https://api.sherpo.io/customer/v1/stores/yourstore.sherpo.io/products/slug:seed-saving-workshop/ticket' \
  --header 'Authorization: Bearer ctk_...'
```

```json title="getTicket 200"
{
  "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_code`** is 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's `null` whenever the ticket doesn't let them in (`status` is `pending`, `waitlisted` or `canceled`), and for a moment while a `going` ticket's code is still being minted. For the second, say the code is on its way and read the ticket again shortly.
- **`status`** is `going` while the ticket lets them in, `pending` or `waitlisted` while their request waits, and `canceled` once it doesn't, with `cancel_reason` (`refunded`, `revoked`, `expired`, `declined`, or `canceled` when the seller canceled the event) and `canceled_at`.
- **`check_ins`** names each session the door let them in at, earliest first. The event's sessions, with their place, are on the [product](/customer-api/reference/get-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.

Source: https://docs.sherpo.io/customer-api/tickets/index.mdx
