Mabel for Business API

Version 1. Connect Mabel to your business's website, CRM or app.

Getting started

In the admin site, under "Developer API", create a key and select its permissions. The key starts withmabel_ and is shown only once. Send it with every request:

Authorization: Bearer mabel_...

The key belongs on your server, not in the browser. For website chat, use the chat snippet from the admin site, which doesn't need a key.

Permissions

PermissionWhat it allows
askAsk Mabel a customer's question, and she answers from the business's knowledge
leadsRead leads and add a lead
appointmentsRead the appointments Mabel booked
actionsAsk whether an action is allowed under the business's policy, and check whether a manager approved it
summaryGet the summary of the last 24 hours

Endpoints

POST /api/v1/ask

A customer's question. You can send question single, or messages with the conversation so far.

curl -X POST https://YOUR-SERVER/api/v1/ask \
  -H "Authorization: Bearer mabel_..." \
  -d '{"question": "What are your opening hours?"}'

{ "reply": "Sunday to Thursday, 8:00 to 19:00...", "actions": [] }

GET /api/v1/leads

Up to the last 200 leads, newest first.

{ "leads": [ { "id": "aB3x", "at": "2026-10-06T07:40:00Z", "name": "Dana", "phone": "0501234567", "need": "Hair color", "channel": "phone", "consent": true, "called": null, "handled": null } ] }

POST /api/v1/leads

Adds a lead. Requires name or phone. Set consent to true only if the customer actually agreed to be called back.

{ "name": "Dana", "phone": "0501234567", "need": "Hair coloring", "consent": true }

GET /api/v1/appointments

{ "appointments": [ { "id": "Q9s1", "name": "Yael", "phone": "0521112222", "when": "Tomorrow at 10:00", "reason": "Scaling", "channel": "phone", "status": "confirmed" } ] }

POST /api/v1/actions/check

Before your system does something on behalf of the business, it asks Mabel. The answer is allowed, needs_approval (with requestId) or blocked. Spending money is never allowed.

{ "action": "give_discount", "detail": "10% for a regular customer" } { "decision": "needs_approval", "requestId": "k2Jd81xQ" }

POST /api/v1/actions/status

{ "requestId": "k2Jd81xQ" } { "status": "approved", "by": "Michal" }

GET /api/v1/summary

{ "text": "In the last 24 hours there were 3 customer inquiries...", "counts": { "asks": 3, "leads": 2, ... } }

Notifications (webhooks)

In the admin site, add an https URL and choose events. Mabel sends a POST for each event and doesn't wait for a response.

EventWhen
lead.createdA new lead came in (phone, website, API or manual)
appointment.confirmedMabel booked an appointment
request.pendingAn action is waiting for manager approval
request.decidedA manager approved or rejected
POST https://your-system/hook x-mabel-signature: 5f2c... (HMAC-SHA256 of the request body, with the secret you received) { "event": "lead.created", "at": "2026-10-06T07:40:00Z", "company": "Smile Clinic", "data": { "id": "aB3x", "name": "Dana", "phone": "0501234567", "need": "Whitening", "channel": "phone", "consent": true } }

Verifying the signature in Node:

const ok = crypto.createHmac('sha256', SECRET).update(rawBody).digest('hex') === req.headers['x-mabel-signature'];

Example: an ElevenLabs agent asking Mabel for permission

An ElevenLabs voice agent can work under the business's policy: before it gives a discount or books something, it asks Mabel. In ElevenLabs, add a Webhook tool to the agent:

FieldValue
Nameask_mabel_permission
Method · URLPOST https://YOUR-SERVER/api/v1/actions/check
HeadersAuthorization: Bearer mabel_... (as an ElevenLabs Secret, with a key that has only the actions)
Body parametersaction (for example give_discount), detail

And in the agent's instructions: "Before a discount or a commitment to a customer, call ask_mabel_permission. If the answer is needs_approval, tell the customer the team will approve it and get back to them. If blocked, don't do it." This way all of the business's agents follow the same rules, and every request is logged in Mabel's log.

Errors and limits

CodeWhen
401No key, or the key was revoked
403The key doesn't have permission for this endpoint
429More than 60 requests per minute for the same key
400Invalid request. The reason is in the field error

Every action through the API is logged in the business's activity log under the key's name.