Sapilon becomes publicly available on 1 December 2026: 42 days to go. The core goes open source the same day →

Ticket Tailor integration

In short

Read events, orders and issued tickets. Connect it on the Integrations page; your app then calls Ticket Tailor through Sapilon without ever holding a Ticket Tailor credential.

Lets your app read your Ticket Tailor box office’s events and event series, the orders placed and the tickets issued.

Connecting

On the Integrations page choose Connect on Ticket Tailor and fill in:

  • API key — Ticket Tailor → Box office settings → API → Generate a new key, with Read access.

Sapilon checks the key with the provider before it saves it, and stores it encrypted; it is never shown again.

What your app can do

Only these requests are available; anything else is refused.

  • GET /overview
  • GET /event_series
  • GET /events
  • GET /events/*
  • GET /orders
  • GET /orders/*
  • GET /issued_tickets

How the agent uses it

Use integrations.request('ticket-tailor', …); paths are relative to https://api.tickettailor.com/v1.

  • GET /overview — the box office.
  • GET /event_series, GET /events (query: { 'start_at.gte': '1760600000' }), GET /events/{id} — with ticket types and how many are left.
  • GET /orders (query: { event_id }), GET /orders/{id}.
  • GET /issued_tickets — query: { event_id }; each has a barcode and status.

Lists come back as { data, links }; continue with starting_after. Read-only.

More from Ticket Tailor: https://developers.tickettailor.com/

Last updated .

Was this page helpful?