SDK overview

Use an IronDome SDK

Use a server-side SDK to check email addresses from your signup flow. All SDKs call https://api.irondome.dev; provide the API key assigned to your account. Keep both values in server configuration and reuse each client for the lifetime of its process or event loop.

Language	Guide	Connection handling
JavaScript / Node.js	Node.js	Reuse one client and its HTTPS pool per process.
Python	Python	Reuse a synchronous client per process or async client per event loop.
Go	Go	Share one client across goroutines.
Rust	Rust	Clone the async client; clones share its pool.

SDKs support one-address checks, bulk checks of up to 100 addresses, and health warmup. The bulk API guide describes result ordering and per-address validation errors.

Construct clients once and close owned resources at final shutdown. Warmup is optional; it sends GET /healthz without an email or API key. It may establish reusable transport state, but does not guarantee a warm detector or a particular connection for a later request.

Checks are not automatically retried or cached. A timeout or cancellation can happen after the service has processed a request, so handle failures separately from an email classification. Keep API keys, request bodies, and email addresses out of logs. See check results and errors.

JavaScript, Go and Rust SDK 0.2.0 are published. Python 0.2.0 is available from public tagged source while PyPI publication is pending. Consult each guide for installation, or see upgrade to SDK 0.2.0.