Leads#
The platform's lead inbox: callback wishes, meeting requests, and chat messages from the website widget.
Public intake (widget)#
POST
/v2/public/leadsThe only open endpoint — CORS for any origin, protected by honeypot and rate limit (10 per IP per minute). Details and fields: website widget.
Console (tenant-bound)#
GET
/v2/leadsThe tenant's leads, newest first (?limit=, max 500):
json
{
"tenant": "bbe",
"items": [
{
"id": "ld_fbfeecef",
"kind": "callback",
"name": "Testkunde",
"phone": "+491701234567",
"preferred_at": "30min",
"page_url": "https://kunde.example/preise",
"status": "new"
}
]
}PATCH
/v2/leads/{id}Maintain the status along the processing path:
| Status | Meaning |
|---|---|
new | Received, unprocessed |
contacted | Customer was reached |
scheduled | Meeting or callback arranged |
done | Completed |
spam | Sorted out |
Planned#
- Automatic callback: an incoming
callbacklead triggers an outbound call through the Voice Runtime (full click-to-call). - Live chat conversations:
chatleads become running chat sessions with an AI first response.