A RESTful JSON API with public endpoints for event listings and an authenticated admin API for reading and editing private data, so you can build custom frontends, integrations, and automations.
Build what you need
The public API gives you access to event listings, availability data,
and booking functionality. No API key is required for public endpoints.
Make HTTP requests and get JSON back.
This means you can build your own event listing page on your existing
website, create a custom booking flow, or pull event data into any system
that can make HTTP requests.
Keys for the admin API
A key stands in for you, so another system can read and change what
you sell without anybody signing in. The site shows the key once, when
it is made, and from then on you see only the name you gave it.
Anyone holding the key can do what you can do, so keep it on a server
you control rather than in the code a browser downloads. A page on
your own website should read the public endpoints, which need no key.
Chobble Tickets does not store the key. It stores a scrambled version
it can check a key against, the same way it stores passwords, so a copy
of the database does not hand anybody your key. You can take one back
at any moment.
The list names each key the owner has handed out, and never shows the key itself. (src)
What the admin API can do
The admin API gives you full CRUD control over
events (create, update, list, delete, and toggle active state), with
attendee endpoints coming next.
Embeddable widget
If you don't want to build a custom integration, Chobble Tickets also
includes an embeddable iframe widget. Drop a snippet of HTML into your
website and your events appear inline.
