# Docs


- **Getting Started**
- [Introduction](/docs): Jetron Fluid lets you sell Jetron Ticket events from your own site, either with an embedded checkout or our API.
- [Quickstart](/docs/quickstart): Make your first Jetron Fluid request in a few minutes.
- [Example site](/docs/example-site): A real event site built on Fluid, using both the embed and the API.

- **Checkout Embed**
- [Checkout Embed](/docs/embed): Sell tickets from your own page with a single iframe, themed to your brand.

- **API**
- [Authentication](/docs/concepts/authentication): Authenticate with your public API key as a Bearer token.
- [Checkout flow](/docs/concepts/checkout-flow): The end-to-end white-label flow, from browsing to reserving to checkout.
- [Reservations](/docs/concepts/reservations): How holds, reservation tokens, and the X-Device-ID header work.
- [Errors](/docs/concepts/errors): The error envelope, status codes, and error_code identifiers.
- [Caching & ETags](/docs/concepts/caching): Conditional requests with ETag and If-None-Match.
- [Money](/docs/concepts/money): All amounts are integers in the smallest currency unit.
- [Pagination](/docs/concepts/pagination): Cursor pagination on the events list.

- **Webhooks**
- [Overview](/docs/webhooks): Get notified on your server when a purchase completes, whichever way you sell.
- [Event types](/docs/webhooks/events): The payloads Jetron sends, and the fields on each one.
- [Verifying signatures](/docs/webhooks/verifying): Confirm a delivery really came from Jetron before you act on it.

- **SDK**
- [Overview](/docs/sdk): @jetronticket/api, a typed zero-dependency client for Jetron Fluid.
- [Client & methods](/docs/sdk/client): createClient options, methods, and the ApiResult envelope.
- [Checkout walkthrough](/docs/sdk/checkout): Build the full reserve → checkout → redirect flow with the SDK.
- [Error handling](/docs/sdk/error-handling): Catch ApiError and branch on stable error codes.
- [Conditional requests](/docs/sdk/conditional-requests): ETag caching with ifNoneMatch and notModified.

- **API Reference**
- [API Reference](/docs/api-reference): Base URL, authentication, and conventions for the Jetron Fluid REST API.
- System: Health and service metadata
  - [Health check](/docs/api-reference/system/health/get): Readiness probe. Postgres and Redis are hard dependencies. The service
reports `503` if either is unreachable. Meilisearch, RabbitMQ, Neo4j and
MongoDB are reported for observability but do not affect the status code.
- Events: Browse a host's public events
  - [List events](/docs/api-reference/events/events/get): Lists the API key host's public events, newest first, with cursor pagination.
  - [Get an event](/docs/api-reference/events/events/slug/get): Fetches a single public event by its slug, scoped to the API key host.
  - [List an event's tickets](/docs/api-reference/events/events/slug/tickets/get): Lists the purchasable ticket types for an event, ordered by their display position.
- Checkout: Reserve tickets and create orders for your attendees
  - [Create or refresh a reservation](/docs/api-reference/checkout/events/slug/reservations/post): Prices the cart and holds the requested stock for the checkout window.
Returns a `reservationToken` and a `quoteReference`. Send the
`X-Device-ID` header to refresh/extend an existing reservation for the
same attendee; omit it to start a new one (a token is minted and
returned). Seat Map events return `400`.
  - [Release a reservation](/docs/api-reference/checkout/events/slug/reservations/delete): Releases a held reservation, freeing the stock. Echo the
`reservationToken` as the `X-Device-ID` header. If omitted, the server
falls back to the reservation held for your client IP + event (the same
fallback used when reserving without a token). Returns `400` if neither
a token nor a matching anonymous reservation is found.
  - [Create an order (checkout)](/docs/api-reference/checkout/events/slug/orders/post): Completes checkout for a held reservation. Echo the `reservationToken`
as the `X-Device-ID` header and send the `quoteReference` from the
reservation response. Free (zero-total) orders are
fulfilled immediately and return `status: confirmed`; paid orders return
`status: pending_payment` and a `checkoutUrl` to redirect the attendee
to. After payment the gateway redirects to your `callbackUrl` with a
`reference` query parameter. A duplicate order for the same reservation
returns `409`.