Ateneo API
Connect your management software (box office, membership, school or event platform) to your organization's events and bookings: read events and availability, create events, push guest lists and pre-bookings, and receive webhook notifications.
Base URL
https://ateneo.app/api/v1
Authentication
Each organization generates its API keys in the admin panel (API section, on paid plans), each with its own permissions. Send the key in the header of every request:
Authorization: Bearer atn_live_…
If your software uses OAuth2, create a client in the same section and exchange its client_id and client_secret for a one-hour token at /oauth/token (client credentials). Send the token the same way as a key.
Endpoints
- POST
/oauth/tokenExchanges client_id and client_secret for a one-hour token - GET
/eventsYour organization's events - POST
/eventsCreates an event on one of your organization's seating charts - GET
/events/{id}One event and its sessions - GET
/events/{id}/availabilitySeating chart capacity and seats taken in each session - PUT
/events/{id}/rosterReplaces the guest list (sent by your management system) - POST
/events/{id}/reservationsPre-books seats in someone's name (from your management system) - GET
/reservations?email=…One person's bookings, by email address - GET
/webhooksYour organization's webhooks - POST
/webhooksRegisters a webhook (its secret is shown only once) - DELETE
/webhooks/{id}Deletes a webhook - POST
/webhooks/{id}/testSends a signed test notification
Example
curl -H "Authorization: Bearer atn_live_…" \ https://ateneo.app/api/v1/events
Webhooks
Register them in the panel or through the API to receive signed notifications of these events. Verify the X-Ateneo-Signature header (format t=…,v1=HMAC-SHA256 of the secret over “timestamp.body”).
reservation.created reservation.cancelled pass.soldout event.published