Dropbox Sign

Install corsair and @corsair-dev/dropboxsign, add the Dropbox Sign plugin, and connect with an API key or OAuth. Then call methods like corsair.dropboxsign.api.account.create() from your app. Corsair stores tokens, and syncs data per tenant.

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

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

Teams use Corsair for e-signature platform for sending, signing, and tracking legally binding document agreements. Common builds include sync jobs, admin tooling, and agents that call Dropbox Sign APIs from your backend. Local DB entities let you query synced Dropbox Sign 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 Dropbox Sign 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/dropboxsign in the open repo. When Dropbox Sign 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 Dropbox Sign data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Dropbox Sign data on your behalf.