Outboundrix
Start free

API documentation

Everything the dashboard does, the API does. Scoped keys, a REST surface, HMAC-signed webhooks, an MCP server and an agent that runs on your own LLM key — all under one permission model.

Outboundrix is pre-launch. The reference below describes the shipping surface; the public base URL and live keys become available at launch. Sections markedPlanned are not callable yet.

API keys

Create a key in Settings, Integrations. Keys are shown once and stored hashed. Each key carries the same role-based scopes that govern the UI and is rate-limited on its own. Send it as a bearer token on every request.

  • Scoped to the same permissions as the dashboard
  • Shown once, stored hashed, revocable at any time
  • Per-key rate limits, separate from the session APIs
Request
curl https://api.outboundrix.io/v1/contacts \
  -H "Authorization: Bearer obx_live_sk_XXXXXXXX" \
  -H "Content-Type: application/json"

One REST surface

https://api.outboundrix.io/v1JSON over HTTPS, separate from the session-cookie dashboard APIs.

GET/v1/contacts

List and filter contacts in the workspace. Supports ICP filters, fit-score thresholds and cursor pagination.

Request
curl https://api.outboundrix.io/v1/contacts \
  -H "Authorization: Bearer obx_live_sk_XXXXXXXX" \
  -H "Content-Type: application/json"
Response
{
  "object": "list",
  "data": [
    {
      "id": "con_3kf9a2",
      "email": "dana@acme.io",
      "full_name": "Dana Ruiz",
      "company": "Acme",
      "fit_score": 0.82,
      "verified": true
    }
  ],
  "has_more": false
}
POST/v1/sequences

Create a branching multichannel sequence. Steps can wait and branch on reply signal, and spam-linting runs server-side before launch.

Request
curl -X POST https://api.outboundrix.io/v1/sequences \
  -H "Authorization: Bearer obx_live_sk_XXXXXXXX" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Q2 Heads of Sales",
    "mailbox_pool": "pool_default",
    "steps": [
      { "channel": "email", "wait_days": 0 },
      { "channel": "email", "wait_days": 3, "if": "no_reply" }
    ]
  }'
Response
{
  "id": "seq_a1b2c3",
  "name": "Q2 Heads of Sales",
  "status": "draft",
  "steps": 2,
  "created_at": "2026-05-17T09:20:00Z"
}
POST/v1/sequences/:id/launch

Launch a draft sequence from a rotated mailbox pool. Returns 409 if the pool is not warmed.

DELETE/v1/api-keys/:id

Revoke an API key immediately. In-flight requests using it fail with 401 on the next call.

Webhooks

Register an endpoint per workspace and Outboundrix posts on domain events: contact.created, reply.received, sequence.finished. Every payload is HMAC-signed with your workspace secret — verify the signature header before trusting the body.

  • Endpoints defined per workspace
  • HMAC signature header on every delivery
  • Exponential backoff with jitter on failure
Delivery
{
  "event": "reply.received",
  "created_at": "2026-05-17T11:04:22Z",
  "data": {
    "contact_id": "con_3kf9a2",
    "sequence_id": "seq_a1b2c3",
    "classification": "interested"
  }
}

MCP server

Planned

A Model Context Protocol server exposes Outboundrix operations as tools: search contacts, enrich, create and launch sequences, read deliverability, read and write the CRM. It authenticates with the same scoped API keys and mirrors the REST capability set, so there is one permission model. Point any MCP-capable model at it.

  • Same scoped keys as REST and the UI
  • Tool surface mirrors the /v1 capabilities
  • Ships in the same deployment
Client configuration
{
  "mcpServers": {
    "outboundrix": {
      "url": "https://mcp.outboundrix.io",
      "headers": {
        "Authorization": "Bearer obx_live_sk_XXXXXXXX"
      }
    }
  }
}

Your key, your model, your cost

Planned

Store your own provider key — OpenAI, Anthropic or Gemini — encrypted per workspace and never in source. An agent runtime executes go-to-market workflows by calling the same tool surface: build a list, draft and launch a sequence, triage replies. The provider adapter is model-agnostic, so your key and your model choice drive both selection and cost.

  • Provider key encrypted per workspace
  • Actions bounded by the API key scopes you grant
  • Every action written to the activity log
  • Provider-agnostic adapter, no token markup

Build on the same system your team uses

Questions about the developer platform go straight to the people who build it. See also how it works.

Developer support

Replies within one business day