Official SDKs with language-specific capability differences
The SDKs do not expose identical surfaces. This page shows the real package names, constructors, auth modes, webhook helpers, and resource coverage for each maintained client.
Last updated May 29, 2026
SDK matrix
TypeScript
Install
npm install bavimailConstructor
new Bavimail({ apiKey })
Auth modes
apiKey, bearer
Webhook helper
verifyWebhookSignature(...) or client.createHandler(...)
Resource coverage
domains aliases attachments analytics emails inboundEmails conversations suppressions tags webhooks
Python
Install
pip install bavimailConstructor
Bavimail(api_key=...)
Auth modes
apiKey
Webhook helper
verify_webhook_signature(...)
Resource coverage
domains aliases attachments analytics emails inbound_emails conversations inbox suppressions tags webhooks
Install and initialize
TypeScript
import { Bavimail } from 'bavimail'
const client = new Bavimail({
apiKey: process.env.BAVIMAIL_API_KEY!,
})Python
from bavimail import Bavimail
client = Bavimail(api_key='YOUR_API_KEY')Which languages and SDKs are supported?
Official TypeScript and Python SDKs are published and documented at /docs/sdks. The REST API is language-agnostic, so any HTTP client works — and the OpenAPI specification at /docs/api is designed to be consumed by agents as tool definitions.
Signed webhook deliveries backed by the real event model
Bavimail emits outbound lifecycle events, inbound receipt events, domain verification events, and test pings. Verification should match the actual SDK helper and header contract.
Use Bavimail with LangChain, CrewAI, LlamaIndex, Vercel AI SDK, Claude Code, Cursor, Cline, and n8n
Bavimail ships @bavimail/toolkit (npm) and bavimail-toolkit (PyPI) with first-party framework adapters, plus a separate @bavimail/mcp-server for MCP-compatible hosts. Every common AI agent workflow integrates through one of these packages.