SDKs

Official TypeScript and Python clients — same resources, same idempotency and webhook verification, idiomatic in each language.

Two official clients. They cover the same API v2 surface with the same resource names, and each is written the way its language expects rather than being a thin translation of the other.

Install

npm install aiinbx

pip install aiinbx

Both read AI_INBX_API_KEY from the environment, so the common case needs no configuration:

import AIInbx from "aiinbx"

const aiinbx = new AIInbx()

const email = await aiinbx.emails.send({
  from: "Ada <ada@example.com>",
  to: "grace@example.com",
  subject: "Hello",
  text: "Sent with AI Inbx.",
})

from aiinbx import AIInbx

with AIInbx() as client:
    email = client.emails.send(
        {
            "from_": "Ada <ada@example.com>",
            "to": ["grace@example.com"],
            "subject": "Hello",
            "text": "Sent with AI Inbx.",
        }
    )

What both give you

Resources

Naming

Two differences to know before you copy a snippet between them.

from is a reserved word in Python, so the Python client uses from_:

{
  from: "Ada <ada@example.com>"
}

{"from_": "Ada <ada@example.com>"}

Everything else keeps the wire name. Request and response fields are snake_case in both — thread_id, scheduled_at, suppression_key — because they’re the API’s names, not the language’s. Only the client’s own options follow each language’s convention: baseURL / base_url, maxRetries / max_retries, idempotencyKey / idempotency_key.

Without an SDK

The API is plain HTTP with bearer auth and JSON bodies. Curl examples run throughout the guides, and the API reference has a request builder per endpoint with generated curl, JavaScript, and Python samples.

Three things to get right if you’re writing your own client: