Authorization: Bearer <key> header.
API keys belong to one project, and every project-scoped call sends that project’s ID in the project header: store the Project ID from Settings → Project → General on the connection (project_id).
Keys only work in the project’s data region. Leave region empty (or eu) for EU projects (https://api.gleap.io/v3); set it to us for US projects (https://api.us.gleap.ai/v3). Settings → Developer → API keys shows the region.
In code, the projectId and baseUrl plugin options override the stored values.
The API needs a Gleap Team plan or higher (Starter has no API access).
What you get:
- 42 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 Gleap API key before the first call: More: API Key
pnpm corsair setup --plugin=gleap --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
boards.list
boards.create
What’s next
API reference
Every
gleap.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.