Integrations

Send email from Rust with reqwest.

From Rust the integration is the JSON API: a serde struct for the payload and one reqwest call. Build the client once with a timeout, send an idempotency key with each message, and verify webhooks with an HMAC over the raw body.

The send

Send an email from Rust.

reqwest = { version = "0.12", features = ["json"] }

let client = reqwest::Client::builder()
    .timeout(std::time::Duration::from_secs(10))
    .build()?;

let response = client
    .post("https://app.usenotix.dev/api/v1/emails")
    .bearer_auth(std::env::var("NOTIX_API_KEY")?)
    .header("Idempotency-Key", "order-4471-receipt")
    .json(&serde_json::json!({
        "from": "Acme <receipts@acme.com>",
        "to": "maria@example.com",
        "subject": "Your receipt",
        "html": "<p>Thanks for your order.</p>"
    }))
    .send()
    .await?;

The from address must be on a domain you have verified in Notix. Step by step: the cURL quickstart and the longer guide to sending email from Rust.

Environment

One API key, kept on the server.

Create an API key on the API keys page of the Notix console and store it as NOTIX_API_KEY in the process environment. Read it only in code that runs on the server, never in anything shipped to a browser.

A Send only key is enough for code that only sends: if it leaks, it cannot read your contacts or delete a domain.

.env

NOTIX_API_KEY=notix_xxxxxxxxxxxx
NOTIX_WEBHOOK_SECRET=whsec_xxxxxxxxxxxx

Webhooks

Verify the signature yourself.

Without an SDK, compute v1= plus the hex HMAC-SHA256 of the X-Notix-Timestamp header, a dot and the raw body, with your signing secret; compare it with X-Notix-Signature in constant time and refuse a timestamp more than 5 minutes old.

Read the body as bytes in your web framework's handler, before deserialising it.

FAQ

Questions, answered.

Is there a Notix SDK for Rust?

No. Notix publishes SDKs for TypeScript, Python and PHP. From Rust the integration is the JSON API over HTTPS, or the SMTP relay, and both send through the same pipeline.

What if the same request runs twice?

Send an Idempotency-Key header (idempotencyKey in notix-js) with a value that names the thing being sent, such as order-4471-receipt. A repeat with the same key and body returns the first result and sends nothing new; the same key with a different body is refused with 409.

Why is my send refused with a from-address error?

The from address must be on a domain you have verified in Notix. Add the domain in the console, publish the DNS records it shows, and wait for verification; until then, sends from that domain are refused.

The free plan does not ask for a card.

Guides