- 5 database entities synced for fast
.search()/.list()queries - 9 incoming webhook event types
Setup
Get credentials
Follow Get Credentials if you need help getting keys.
Store credentials
- Solo
- Multi-Tenant
api_key=, bot_token=, or OAuth client fields).Authentication
Each tab shows how to register the plugin for that authentication method. The defaultauthType from the plugin does not need to appear in the factory call.
- API Key (Default)
- OAuth 2.0
corsair.ts
pnpm corsair setup --plugin=telegram (see Get Credentials for field names). For OAuth, you typically store integration keys at the provider level and tokens per account or tenant.More: API KeyWebhooks
This plugin registers 9 webhook handler(s). Configure your provider to POST events to your Corsair HTTP endpoint, then usewebhookHooks in the plugin factory for custom logic.
See Webhooks for every event path and payload shape, and Webhooks concept for how to set up routing.
Query synced data
Synced entities supportcorsair.telegram.db.<entity>.search() and .list(). See Database for filters and operators.
Example API calls
Read-style (read):—
No read-style endpoint inferred; pick any operation from the reference below.
Write-style (write): —
No write-style endpoint inferred; pick any operation from the reference below.
See the full list on the API page. Use pnpm corsair list --plugin=telegram and pnpm corsair schema <path> locally to inspect schemas.
Hooks
Usehooks on API calls and webhookHooks on incoming events to add logging, approvals, or side effects. See Hooks and the Webhooks page for payload types.
Reference
| Topic | Link |
|---|---|
| API | API |
| Database | Database |
| Webhooks | Webhooks |
| Credentials | Get credentials |