SDKs
Pick your language. The SDKs are thin, typed wrappers around the REST API plus a built-in webhook signature verifier — same wire format, same auth, same quota.
| Language | Package | Status |
|---|---|---|
| Node.js / TypeScript | @mittr/sdk-node | Stable (v0.1) |
| Python | mittr | Coming soon |
| Go | github.com/silvendynamics/sdk-go | Coming soon |
| Ruby | mittr | On request |
What they cover
Section titled “What they cover”Every official SDK ships three things:
- A typed client for the REST API —
events.send(),events.list(),endpoints.create(), etc. Idempotency keys are generated automatically; cursor pagination is exposed as an async iterator. - A standalone signature verifier — call one function with the secret, the request headers, and the raw body. Constant-time compare, default 5-minute timestamp tolerance, no framework dependency.
- A request handler — drop-in middleware for the language’s idiomatic web framework (Express / Connect on Node, ASGI on Python,
net/httpon Go).
Pricing
Section titled “Pricing”SDKs are open source under the MIT License and calls through them are billed identically to raw HTTP — same plan quota, same overage rates. No SDK markup, no SDK discount. The one indirect win: SDK send() calls auto-generate idempotency keys, so your own retries don’t double-bill or double-deliver.
Not on this list?
Section titled “Not on this list?”If your stack isn’t listed, the REST API is the lowest common denominator — see the REST API guide and the live spec. Open an issue on the SDK repo and tell us which SDK you’d reach for first.