Public API endpoints

These endpoints are open — no authentication required. They let you build your own ticketing flow: display events, show ticket types, manage a shopping cart, and create an order that redirects the user to the payment provider.

Typical workflow

1. Pick an event: GET /events → choose a sub_event from the returned list.
2. Pick a ticket type: GET /tickettypes/:event_id → choose a discount_id.
3. Create a cart: POST /cart/ → you get a cart_id.
4. Add seats: POST /cart/:cart_id with event_id, numberoftickets, discount_id.
5. Create the order: POST /order/create with the cart and customer details → you get a payment URL.
6. Redirect the user to the payment URL.
7. Check status after payment: GET /order/:order_key.

Endpoints

Step	Endpoint	Doc
1	GET /v1/:client/events[/:id]	Events
2	GET /v1/:client/tickettypes/:event_id	Ticket types
3	POST /v1/:client/cart/	Cart
4	POST /v1/:client/cart/:cart_id	Cart
5	POST /v1/:client/order/create	Order
7	GET /v1/:client/order/:order_key	Order

Privacy note

Public endpoints obfuscate sensitive information. The reported event_free capacity is always the maximum number of tickets allowed per order (with offline-reserved tickets taken into account) — never the actual number sold or remaining.

Rate limits

Be respectful with requests:

• Cache event lists for at least a few minutes on your side.
• Don't poll the cart on a timer — only query when the user interacts.
• If you anticipate very high traffic (e.g. major on-sale), let us know in advance.

---

See also: API overview · Peppered endpoints (authenticated)