Skip to main content
Use Fireberry through Corsair: one client, typed API calls. Configure an API key in Corsair. Fireberry REST and Batch endpoints send it as the tokenid header; Metadata API calls follow the documented tokenid query parameter. API route inventory: 244 documented method/path operations across REST, Metadata, and Batch; 243 are dispatched by the generic typed Corsair operations. The Date & Time custom field update route is excluded because its published path and parameter contradict one another. No inbound webhook contract is published in the API index, so webhooks are not exposed. What you get:
  • 24 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

Inspect an account field
Create an account with the Batch API
See the full list on the API page.

What’s next

API reference

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