← All integrations

UniOne

30 operations2 webhooks

Transactional email service for sending bulk mail, templates, and deliverability management.

Supported operations

  • DeleteDestructive

    Tool to delete a sender domain from the account. Use only when you are certain: the domain must be re-added and re-verified to send from it again.

  • ManageWrite

    Tool to inspect and verify sender domains: fetch DNS records, trigger a verification or DKIM check, or list domains. Deleting a domain is a separate tool.

Supported triggers

  • Email Status

    Transactional email status events from UniOne

FAQ

Install corsair and @corsair-dev/unione, add the UniOne plugin, and connect with an API key. Then call methods like corsair.unione.api.domain.delete() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. UniOne requires an API key from your UniOne account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

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

Teams use Corsair for transactional email service for sending bulk mail, templates, and deliverability management. Common builds include sync jobs, admin tooling, and agents that call UniOne APIs from your backend. Webhook handlers react to UniOne events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced UniOne 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 UniOne 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/unione in the open repo. When UniOne 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 UniOne data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store UniOne data on your behalf.