Set a client up from your own code

Authentication

Every request carries the client's API key as a bearer token. The client creates it in their dashboard under Account → API keys; it is shown once. The key identifies the tenant, so no endpoint takes a tenant id — you cannot reach another account's data by construction, not by a check somebody remembered to write.

curl https://sipmind.net/api/v1/agent/config \
  -H "Authorization: Bearer sk-tenant-YOUR_KEY"

Quickstart: zero to answering

Four calls. The client registers themselves and gives you a key; everything after that is yours.

curl -X PATCH https://sipmind.net/api/v1/agent/config \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{
    "prompt_mode": "layered",
    "business_context": "Dental clinic in Almaty. Mon-Sat 9-19. Cleaning 15000 KZT, implant from 250000 KZT. Address: Abay 15.",
    "welcome_message": "Здравствуйте! Клиника «Дента». Слушаю вас.",
    "timezone": "Asia/Almaty"
  }'

curl -X POST https://sipmind.net/api/v1/documents \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"content": "Отбеливание Zoom 4 — 90000 ₸, занимает 60 минут…"}'

curl -X POST https://sipmind.net/api/v1/channels/telegram \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"bot_token": "123456:AA..."}'

# WhatsApp, when the number already sits on a Meta app you manage.
# phone_number_id is the numeric id from WhatsApp Manager — not the phone number.
curl -X POST https://sipmind.net/api/v1/channels/whatsapp \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"phone_number_id": "1236893399497040", "access_token": "EAA..."}'

# check every channel at once, including the half-connected ones
curl https://sipmind.net/api/v1/channels -H "Authorization: Bearer $KEY"

curl "https://sipmind.net/api/v1/leads?updated_since=2026-08-01T00:00:00Z" \
  -H "Authorization: Bearer $KEY"

# → {"leads": [...], "count": 12,
#    "next_updated_since": "2026-08-12T09:14:02.881Z", "has_more": false}

Keeping in sync

Lists are ordered by updated_at ascending and cursored on it. Store the next_updated_since you get back and pass it in next time; keep going while has_more is true.

Ascending is not a style choice. Newest-first with an offset loses rows: while you page through, new rows land at the top and push the boundary, so page two repeats some and skips others. With an ascending cursor a changed row moves to the end — which is where your next poll meets it.

Let your coding agent do it

If you already work in Claude Code, Codex or another MCP client, you do not have to write the calls yourself. One file, no dependencies, any Python 3.10+:

curl -O https://sipmind.net/mcp/sipmind_mcp.py

Run that in your project folder, then point your agent at it — for Claude Code, .mcp.json beside it:

{
  "mcpServers": {
    "sipmind": {
      "command": "python3",
      "args": ["./sipmind_mcp.py"],
      "env": { "SIPMIND_API_KEY": "sk-tenant-YOUR_KEY" }
    }
  }
}

The path is relative, so start the agent from that folder — or write the full path instead. If the first call answers that your Python cannot verify certificates, that is your machine's trust store, not us: run Install Certificates.command (macOS python.org builds) or pip install certifi.

After that you can simply say what you want: “describe this clinic to the agent from their website, connect the Telegram bot, load the price list, and show me the leads from the last week.” Fourteen tools cover configuring the agent, connecting channels — including routing a WhatsApp number you already manage — the knowledge base, and reading leads, conversations and contacts.

Events pushed to you

Polling is the reliable path; events are the fast one. Subscribe and we POST to your endpoint when something happens — lead.created the moment the AI captures a lead, lead.stage_changed when it moves, appointment.created when one is booked.

A new account receives lead.created only, so say which events you want — GET /events/subscription lists everything available.

PUT /api/v1/events/subscription
{
  "url": "https://your-endpoint.example/hook",
  "events": ["lead.created", "lead.stage_changed", "appointment.created"],
  "signing_secret": "<16+ characters you choose>"
}

The secret is write-only: we report whether one is set, never its value. Then every delivery looks like this.

POST https://your-endpoint.example/hook
X-SIPmind-Event: lead.created
X-SIPmind-Signature: sha256=<hmac of the raw body with your secret>

{
  "event": "lead.created",
  "tenant_id": "0de00000-…",
  "occurred_at": "2026-08-13T04:12:07.881Z",
  "data": {
    "lead_id": "9f2c…", "contact_id": "3a71…",
    "name": "Anna", "phone": "+77001234567", "email": "",
    "source": "whatsapp", "stage": "new", "message": "…"
  }
}

Verify the signature against the raw body before trusting it. We retry a 5xx or a timeout three times with growing gaps; a 4xx is treated as your endpoint saying "don't", and we stop.

Endpoints

Full request and response shapes: the OpenAPI schema — point your generator at it.

Things worth knowing before you build

What the API does not do yet

So you can plan around it rather than discover it:

• Creating an account. Clients register themselves; you work with their key.
• Connecting WhatsApp and Instagram — those run through the dashboard's one-click flow, because the token exchange happens on Meta's side and needs a browser.
• Managing AI employees and practitioners.
• Deleting contacts, calls or conversations. Ask us and we will do it — a partner key should not be able to erase a client's history.

Need one of these? Write to hello@sipmind.net — this list is ordered by what people ask for.