What you can build
- Sell tickets on your site Show your events and take orders on your own website, with EOS's hosted checkout or one you build with Stripe's Payment Element.
- Scan at the door Run your own scanning app or turnstiles against the same door rules as the EOS scanner: gates, re-entry, ages and staff passes.
- Keep your systems in step Send every order, refund and check-in to your CRM, mailing list or data warehouse the moment it happens, with signed webhooks.
How it works
- A REST API over HTTPS at
https://eos.aveoevents.com/api/v1. Requests and responses are JSON; times are UTC in ISO 8601; money is in the event’s currency, in pounds and pence (25.5 is £25.50). - Each website, app or system gets its own key, made by an admin in EOS on the API keys page, with only the 16 permissions it needs, an expiry and, if you like, the IP or web addresses it may be used from.
- Secret keys stay on your servers. Publishable keys can sit in web pages: they only read the company and its events and create checkouts, and only from the web addresses you allow.
- 20 kinds of webhook event tell your systems the moment something happens anywhere in EOS (the API, the console, the shop, the door or Stripe), signed with the Standard Webhooks scheme and retried for hours if your server is down.
- Every company has a sandbox to build against first: test keys (
eos_sk_test_), Stripe’s test cards and webhooks marked"livemode": false. - Keys are stored hashed, locked to the permissions, addresses and limits you choose, and every request is logged. How the API is kept safe.
- The API is versioned by date. This is version
2026-11-15, sent back on every response in theAVEO-Versionheader.
Your first call
Once you have a key, ask the API who it belongs to. Keep the key in an environment variable such as EOS_API_KEY, never in code you share.
curl https://eos.aveoevents.com/api/v1 \
-H "Authorization: Bearer $EOS_API_KEY"{
"object": "api_key",
"livemode": true,
"kind": "secret",
"name": "Website",
"scopes": [
"events:read",
"checkout:write"
],
"expires_at": null,
"rate_per_minute": 120,
"company": {
"id": 12,
"slug": "acme-events",
"name": "Acme Events"
}
}Next: the quickstart takes you from a new key to a paid order in six steps.
The API at a glance
- The API keyWho you are, what your key may do, and the company it belongs to.2 endpoints
- EventsYour events with their dates, venue and ticket types, and live availability.5 endpoints
- CheckoutSell tickets from your own site: hold them, take the buyer's details, then payment.4 endpoints
- OrdersEvery order, paid or not: read them, cancel, refund, mark paid and resend tickets.6 endpoints
- GuestsTicket holders for an event: names, emails, ticket types and whether they are inside.4 endpoints
- Check-insScan tickets in and out from your own door app, with gates and re-entry.2 endpoints
- Discount codesCodes buyers type at checkout, on one event or many.3 endpoints
- EnquiriesMessages from your own contact form, straight into Customer cases.1 endpoints
- ReportsSales by day for one event or all of them.1 endpoints
- Webhook endpointsAddresses EOS calls when something happens, signed so you can trust them.9 endpoints
For code generators, Postman and Insomnia: the OpenAPI 3.1 document.
Getting access
The API comes with EOS, the software AVEO runs its own events on. If your company is on EOS, an admin can make keys today on the API keys page. If it is not yet, ask AVEO for a quote.