SDKs & languages

Every Drin capability is reachable from one account and one key. Use the typed SDK in your language, the CLI for scripts and CI, the MCP server for agents — or talk to the REST API directly from anything that speaks HTTP.

TypeScript / Node

@drin00/sdk — typed client with retries, cursor pagination, and webhook verification.

Python

pip install drin — the official Python client, same surface as the TS SDK.

Go

Call the REST API with the standard net/http client — worked example below.

Ruby

Use Net::HTTP or your HTTP client of choice against the REST contract.

PHP

A few lines of curl or Guzzle — the same JSON body as everywhere else.

cURL / REST

No dependency. The raw HTTP contract, callable from any stack.

Install

npm install @drin00/sdk

pip install drin

npx -y @drin00/cli send --to you@example.com --subject "Hi" --text "It works"

TypeScript / Node

The official client mirrors the wire contract one-to-one, with built-in retries, async-iterator pagination, typed errors, and local webhook verification.

import { DrinClient } from "@drin00/sdk";

const drin = new DrinClient({ apiKey: process.env.DRIN_API_KEY! });

const { id } = await drin.emails.send({
  from: { email: "hello@acme.com", name: "Acme" },
  to: [{ email: "customer@example.com" }],
  subject: "Welcome aboard",
  html: "<h1>You're in</h1>",
});

Python

Same surface, Pythonic names. Published to PyPI as drin.

import os
from drin import DrinClient

drin = DrinClient(api_key=os.environ["DRIN_API_KEY"])

msg = drin.emails.send(
    from_={"email": "hello@acme.com", "name": "Acme"},
    to=[{"email": "customer@example.com"}],
    subject="Welcome aboard",
    html="<h1>You're in</h1>",
)
print(msg["id"])

Any language (REST)

No SDK? Every endpoint is a plain JSON request over HTTPS. Here’s the same send in Go, Ruby, and PHP.

body, _ := json.Marshal(map[string]any{
    "from":    "Acme <hello@acme.com>",
    "to":      "customer@example.com",
    "subject": "Welcome aboard",
    "html":    "<h1>You're in</h1>",
})
req, _ := http.NewRequest("POST", "https://api.drin.run/v1/emails", bytes.NewReader(body))
req.Header.Set("Authorization", "Bearer "+os.Getenv("DRIN_API_KEY"))
req.Header.Set("Content-Type", "application/json")
resp, _ := http.DefaultClient.Do(req)

require "net/http"
require "json"

uri = URI("https://api.drin.run/v1/emails")
req = Net::HTTP::Post.new(uri, {
  "Authorization" => "Bearer #{ENV['DRIN_API_KEY']}",
  "Content-Type"  => "application/json",
})
req.body = { from: "Acme <hello@acme.com>", to: "customer@example.com",
             subject: "Welcome aboard", html: "<h1>You're in</h1>" }.to_json
Net::HTTP.start(uri.host, uri.port, use_ssl: true) { |http| http.request(req) }

$ch = curl_init("https://api.drin.run/v1/emails");
curl_setopt_array($ch, [
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer " . getenv("DRIN_API_KEY"),
    "Content-Type: application/json",
  ],
  CURLOPT_POSTFIELDS => json_encode([
    "from" => "Acme <hello@acme.com>",
    "to" => "customer@example.com",
    "subject" => "Welcome aboard",
    "html" => "<h1>You're in</h1>",
  ]),
]);
$response = curl_exec($ch);

Account-wide keys also take a sender (your project’s external id) so requests are scoped correctly. Project-scoped keys don’t need it.

Get started

Sending

Receiving

Domains & deliverability

Agents & SDKs

Account

SDKs & languages

TypeScript / Node

Python

Go

Ruby

PHP

cURL / REST

Install

TypeScript / Node

Python

Any language (REST)

TypeScript / Node

Python

Go

Ruby

PHP

cURL / REST

​Install

​TypeScript / Node

​Python

​Any language (REST)

Install

TypeScript / Node

Python

Any language (REST)