pnpm add corsair @corsair-dev/eventee. Before calling this plugin, generate a per-event API token in the Eventee admin and configure it as the plugin API key. The generated API-key prompt only stores a token you already created; it does not provision Eventee credentials. API access is available on selected Eventee plans. The token scopes all requests to one event.
What you get:
- 31 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)
Store the Eventee API key before the first call: More: API Key
pnpm corsair setup --plugin=eventee --tenant=acme api_key=<your-key> (leave out --tenant without multiTenancy), or pass it as key in the plugin options. With Hub, each tenant enters their own key on the connect page. See API key auth.First create an API token in the Eventee admin settings for the target event, then enter it when Corsair prompts for the API key. Corsair cannot create or regenerate this provider token.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
attendees.get
session.post
What’s next
API reference
Every
eventee.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.