Seaty Developer API
The Seaty Developer API lets your organisation read its own events, dates, orders, tickets, attendees and payments, and record external balance payments, all over a simple REST API.
The Seaty Developer API is a read-and-record REST API that lets your own systems work with your organisation's own data: events, dates, orders, tickets, attendees, payments and discounts. It is built for organisers who want to sync Seaty with accounting tools, CRMs, dashboards, or their own back-office systems.
Who this is for: technical staff (or a developer working on your behalf) at an organisation that sells tickets on Seaty. You do not need to be a Seaty employee, and you do not need any special arrangement: any organisation super-admin can create an API key and start using it.
What you can do
- Read your events and their dates, including ticketing settings and ticket categories.
- Read orders placed on your events, with the full money breakdown, the tickets on each order, the payments and refunds against it, and any discount codes used.
- Read attendees (everyone who has ordered) for marketing or CRM sync.
- Read a per-date sales-and-attendance summary so a dashboard does not have to add up every order itself.
- Record external balance payments (cash, cheque, card taken outside Seaty, or bank transfer) against an event, with the same validation and receipt emails as the Seaty admin tools.
What it is not
- It is scoped to your own organisation only. A key can never read another organisation's data. Every request is filtered to the organisation the key belongs to.
- It is read-only apart from balance payments. You cannot create or cancel orders, edit events, or issue card refunds through the API. Those stay in the Seaty admin tools.
- It is not a public data feed. Keys are private credentials. Treat them like passwords.
The basics at a glance
| Base URL | https://developer.seaty.co.uk |
| Version | All endpoints are under /v1 |
| Authentication | Authorization: Bearer sk_live_... (your API key) |
| Format | JSON. Money is in minor units (pence). Dates are ISO 8601. |
| Pagination | ?page= and ?per_page= (max 100), with a data / links / meta envelope |
| Interactive reference | https://developer.seaty.co.uk/docs (live OpenAPI / Swagger) |
A first call looks like this:
curl "https://developer.seaty.co.uk/v1/events?per_page=5" \
-H "Authorization: Bearer sk_live_your_key_here"
Where to go next
- Getting started: create a key and make your first request.
- Authentication and keys: how keys, scopes and security work.
- Requests and responses: pagination, money, dates, errors and rate limits. Read this once; it applies to every endpoint.
- Endpoint guides: Events, Event dates, Orders, Attendees, Balance payments.
- Reference: the full endpoint list, payment-method codes, scopes and error codes on one page.
Need help? Email support@seaty.co.uk.