Close

Install corsair and @corsair-dev/close, add the Close plugin, and connect with an API key or OAuth. Then call methods like corsair.close.api.activities.createCall() from your app. Corsair verifies webhooks, stores tokens, and syncs data per tenant.

Yes. Close supports an API key or OAuth. Use credentials or OAuth scopes that match what you automate. Create them in the Close developer console, then paste into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Close, GitHub, Notion, Stripe, and the rest. Trigger Close from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for close plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call Close APIs from your backend. Webhook handlers react to Close events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Close records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Close API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/close in the open repo. When Close ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Close data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Close data on your behalf.