Skip to main content
Use SuperSaaS through Corsair: one client, typed API calls. SuperSaaS uses HTTP Basic auth: the account name is the username and the API key the password. Store the key as the API key and the account name as account_name on the account. The key is under Account Info, API Key.
  • Every booking and slot call names its schedule. schedule_id is sent as a query parameter; without it SuperSaaS answers 404.
  • Creates return the new id. SuperSaaS answers 201 with an empty body and the new record’s URL in Location; the plugin returns { created, id, location }. Updates and deletes answer an empty 200 and return { id, updated } or { id, deleted }.
  • Bookings can email the customer. A schedule set to send confirmations emails the customer on a booking create or change, so both are marked destructive. Turn confirmations off on the schedule’s Process tab for test runs.
  • Schedule reads answer an envelope. schedules.changes, range, agenda and free return { bookings } or, on a capacity schedule, { slots }.
What you get:
  • 20 typed API operations

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

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 recent schedule changes
Create a booking
See the full list on the API page.

What’s next

API reference

Every supersaas.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.