AI AI-generated. The people shown do not exist.
One interface, included in every plan
Gibt es eine Schnittstelle?
Ja, in jedem Tarif. HTTP und MCP, mit einem Schlüssel aus Ihrem Konto.
Create bots, maintain the knowledge base, read conversations, ask questions — with the same key straight from an AI assistant. Only the pace differs between plans.
- 39
- REST endpoints
- 35
- MCP tools
- 4
- Webhook events
The first call
GET api/v1/me
Authorization: Bearer waa_…If it answers, the token works — and the response tells you which team it belongs to and which rights it carries.
What the interface can do
This list is not written, it is counted: it comes from the same description that also produces the reference in your account area and the machine-readable version.
Account
-
GET
api/v1/meDetails about the token in use
Bots
-
GET
api/v1/botsList the team's bots -
POST
api/v1/botsCreate a bot -
GET
api/v1/bots/{bot}Read a bot -
PATCH
api/v1/bots/{bot}Update a bot -
DELETE
api/v1/bots/{bot}Delete a bot -
GET
api/v1/bots/findBot über die Domain finden
Widget
-
GET
api/v1/bots/{bot}/widgetRead the widget design -
PATCH
api/v1/bots/{bot}/widgetUpdate the widget design
Knowledge base
-
GET
api/v1/bots/{bot}/pagesList knowledge base pages -
PATCH
api/v1/bots/{bot}/pages/{page}Update a page -
DELETE
api/v1/bots/{bot}/pages/{page}Delete a page -
POST
api/v1/bots/{bot}/crawlTrigger a crawl -
POST
api/v1/bots/{bot}/reindexRe-index -
GET
api/v1/bots/{bot}/pages/{page}Eine Seite samt Abschnitten lesen -
PATCH
api/v1/bots/{bot}/chunks/{chunk}Einen Abschnitt ändern
Conversations
-
GET
api/v1/bots/{bot}/conversationsList conversations -
GET
api/v1/bots/{bot}/conversations/{conversation}Read a conversation -
GET
api/v1/bots/{bot}/conversations/{conversation}/messagesRead a conversation's messages
Chat
-
POST
api/v1/bots/{bot}/messagesAsk the bot a question
Analytics
-
GET
api/v1/bots/{bot}/analyticsAnalytics for one bot -
GET
api/v1/bots/{bot}/analytics/low-confidenceUnsichere Antworten
Webhooks
-
GET
api/v1/webhooksWebhook-Ziele auflisten -
POST
api/v1/webhooksEin Webhook-Ziel anlegen -
DELETE
api/v1/webhooks/{webhook}Ein Webhook-Ziel löschen -
GET
api/v1/webhooks/{webhook}/deliveriesZustellversuche eines Ziels lesen
Wissenslücken
-
GET
api/v1/bots/{bot}/gapsWissenslücken auflisten -
PATCH
api/v1/bots/{bot}/gaps/{gap}Eine Lücke ändern -
POST
api/v1/bots/{bot}/gaps/{gap}/resolveEine Lücke beantworten -
DELETE
api/v1/bots/{bot}/gaps/{gap}Eine Lücke löschen
Korrekturen
-
GET
api/v1/bots/{bot}/correctionsKorrekturen auflisten -
POST
api/v1/bots/{bot}/correctionsEine falsche Antwort korrigieren -
PATCH
api/v1/bots/{bot}/corrections/{correction}Eine Korrektur ändern -
DELETE
api/v1/bots/{bot}/corrections/{correction}Eine Korrektur löschen
Content-Vorschläge
-
GET
api/v1/bots/{bot}/suggestionsContent-Vorschläge auflisten -
POST
api/v1/bots/{bot}/suggestions/analyzeNeue Analyse anstossen -
GET
api/v1/bots/{bot}/suggestions/{suggestion}Einen Vorschlag lesen -
PATCH
api/v1/bots/{bot}/suggestions/{suggestion}Einen Vorschlag annehmen oder ablehnen
Description
-
GET
api/v1/openapi.jsonThe machine-readable description of this API
The key
You create it yourself and revoke it whenever you like. It is shown in plain text exactly once — after that nobody can show it again, not even us.
In your account area under
api-zugang
Pace, not access tiers
Access is the same in every plan, the free one included. The only difference is how many requests per minute get through.
The exact tiers live with the plans, because that is where they are maintained. A second list here would sooner or later be the wrong one.
MCP: the same key, for AI assistants
Ask your AI assistant how many conversations the shop bot had yesterday: it looks the answer up itself instead of you digging out a report. All it needs is the same key, there is nothing to build.
- Endpoint
api/mcp- Authentication
Authorization: Bearer- MCP tools
- 35
Webhooks
Instead of asking, you get called. Every delivery carries an HMAC-SHA256 signature with a timestamp, so you can verify that it came from us and was not replayed.
conversation.startedconversation.endedmessage.createdlead.captured
The signature sits in the header
X-WAA-Signature.
You register your own targets in the account area under API access, or through the API itself; the same place lists the last delivery attempts with the response code your server returned.
No account yet? Try it free for 30 days