x-api-key header. Create a key in your
Eventzilla account under Settings > Developers > API Credentials, then
save it for the eventzilla integration.
The checkout workflow runs in four steps and each one needs the event’s
dateid, not its id: checkout.prepare (what is on sale, and the
payment_id to use), checkout.create (reserve, and get one
ticket_price_id per ticket), checkout.fillOrder (buyer and attendee
details), then checkout.confirm (record the payment). A reservation holds
inventory until it is confirmed or abandoned.
Eventzilla posts webhooks, but does not sign them and documents no secret to
verify one with, so this plugin registers no inbound webhook: a delivery
cannot be told apart from a forged request.
List operations page with offset and limit; each result carries
next_offset, which is null on the last page. events.get,
attendees.get and users.get answer an array, and an empty one for an
unknown id rather than a 404. transactions.get answers an array too, but
an unknown reference is a 404 error, not an empty result.
What you get:
- 20 typed API operations
Setup
1
Install
2
Add the plugin
corsair.ts
multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.3
Choose authentication
- API Key (Recommended)
No setup required yet. When you make your first request as a tenant, Corsair prompts for the API key.More: API Key
4
Connect a tenant
Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.
Example API calls
List the account’s live eventsWhat’s next
API reference
Every
eventzilla.api.* operation with input and output types.Connect / OAuth
createLink, Hub delivery, and tenant connect flows.
Use with agents
Expose this plugin’s operations as MCP tools.