signedData string and a hex ECDSA signature over it; verify them with the PEM public key from webhooks.getPublicKey (store it with keys.set_webhook_signature or set it as the plugin’s webhookSecret). That key is the same for every Passcreator account, so webhooks.subscribe also adds a corsair_token query parameter to the target URL, derived from the account’s API key; the handler refuses deliveries whose URL lacks this account’s token. Create subscriptions through webhooks.subscribe (not the Passcreator dashboard), and create them again after rotating the API key.
Every operation is described in the official docs: https://developer.passcreator.com/en
What you get:
- 21 typed API operations
- 1 incoming webhook event types
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 Passcreator API key before the first call: More: API Key
pnpm corsair setup --plugin=passcreator --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.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
Read a passWebhooks
This plugin registers 1 webhook event type. Configure the provider to POST to your Corsair HTTP handler, then usewebhookHooks on the plugin factory.
See Webhooks for every event path and payload shape, and Webhooks concept for routing.
What’s next
API reference
Every
passcreator.api.* operation with input and output types.Webhooks
Event paths, payloads, and
webhookHooks examples.Connect / OAuth
createLink, Hub delivery, and tenant connect flows.
Use with agents
Expose this plugin’s operations as MCP tools.