Talkward × API
Connect your own systems to the inbox
Connect your own systems to the inbox: read conversations, send messages, set status and fields, learn via webhook when something happens. A documented REST API with JSON and your own keys, no extra cost from Professional.
Sound familiar? Three moments where ready-made building blocks are not enough.
Zapier, Make and n8n cover a lot. But some systems are home-built, run in-house or should talk without a detour.
The ERP is home-written.
No connector fits, no marketplace block knows it. Still the AI should know the order status from it, and your team should see the customer number next to the conversation.
The ticket system stays.
Complaints have run in your own system for years, with deadlines and reports. What is handed over in chat has to land there as a case, automatically.
Monitoring should reach the team.
The store has a problem, a hundred customers write at once. Your team learns it from the inbox, not from the monitoring that has known for ages.
With the API your system talks to Talkward directly, both ways, with a key you can revoke at any time. Make, Zapier and n8n use the same API.
Three integrations merchants build first
What a developer gets done in an afternoon.
All calls are JSON over HTTPS with a bearer key. The API itself provides examples from your real conversations.
Own system → fields in the conversation
On every new customer message (webhook) your system looks up customer number and order status and writes both as fields into the conversation. Your team and the AI see them next to the chat.
Handover → case in your own ticket system
When the AI hands over to the team, your system creates a case with the summary and writes the case number back as a note. Done in the ticket system, done in Talkward.
Outage → notification to the team
When your monitoring reports an outage, your script sends an urgent notification into the inbox’s team channel. The team knows before the first customer writes.
How the API worksRead, write, webhooks.
The API lives at chat.talkward.app/api/v1. You create a key under Extensions and send it as a bearer token. Read: conversations, messages, contacts, brands, team. Write: message in a conversation, new message to a contact by email or WhatsApp, note, status, assignment, tags, fields, contact. Webhooks report seven events to your address, signed. Plus notifications into team channels. All responses are JSON with ok and an error code when something is missing.
Documented, with real examples
Every route with fields, error codes and responses. For webhooks the API provides example payloads from your real conversations. The public docs page is in preparation; until then it is on the setup page.
Seven webhook events
New customer message, sent message, new conversation, handover to the team, closed, assignment, tag. Optionally for one brand only. Every delivery is HMAC-signed, failed ones are retried.
One key per system
A key belongs to one workspace and sees only its data. You create one per system and revoke it there. 300 requests per minute per key.
Servers in Nuremberg
The API runs on the same servers as the inbox, in ISO/IEC 27001:2022-certified data centres in Nuremberg. No third party in between when you integrate yourself.
- Connection
- REST API /api/v1 with JSON and bearer key, webhooks with signature
- Access
- Conversations, messages, contacts, brands, team (read); messages, notes, status, assignment, tags, fields, contact (write)
- Processing
- Nuremberg (ISO 27001), Cologne, Paris. “Europe only” option. Credentials stored encrypted, orders only cached briefly.
What your system writes sits in the conversation.
Fields, notes, tags and messages from the API look like everything else in the inbox: with time and the key’s name as sender. Your team sees what happened automatically, and the AI uses the fields for its replies.
- Fields from your system
- Notes
- Tags
- Status
- Webhook events
- Key per system
- Customer number
- K-88213 (from own ERP)
- Shipping status
- Shipped, 24 Sep (field via API)
- Case
- T-4711 in the ticket system
- Last webhook
- uebergabe, 25 Sep, 09:41
Set up in three steps.
From Professional, no extra cost. You need somebody who knows HTTP and JSON; nothing else.
Create a key
In Talkward under Settings › Extensions › API create a key. It starts with tw_ and is shown only once.
Screenshot to followCheck the connection
Call GET /api/v1/ich with the key. The response names your workspace and the key. Then GET /gespraeche for the first real data.
Screenshot to followCreate a webhook
POST /webhooks with event and your HTTPS address. Talkward returns a secret for the signature and example payloads from your conversations for testing.
Screenshot to follow
Included in Professional
no extra costfrom Professional, provisional, net
No extra cost from Professional, nothing extra to book. The same API that Make, Zapier and n8n build on.
All plans and prices- Read conversations, messages, contacts, brands and team
- Send messages, set notes, status, assignment, tags, fields and contact
- Seven webhook events, signed, with examples from your data
- Notifications into team channels, own keys per system
- Servers in Nuremberg (ISO 27001)
- Data processing agreement
- AI replies labelled (EU AI Act)
- Extensions cancellable monthly
Questions about the API
Question not listed? Write to us at hey@talkward.app.
What can the API do?
Read: conversations, messages, contacts, brands, team. Write: message in a conversation, new message to a contact by email or WhatsApp, note, status, assignment, tags, fields, contact. Plus webhooks for seven events and notifications into team channels.
Where do I find the documentation?
On the extension’s setup page, with all routes, fields and error codes. The public docs page on talkward.app is in preparation. Example payloads for webhooks come from your real conversations via the API.
How secure are the keys?
A key belongs to exactly one workspace and sees only its data. You create one per system and revoke it at any time. Webhook deliveries are HMAC-signed, 300 requests per minute apply per key.
Do I need the API if I use Zapier or n8n?
No. Zapier, Make and n8n bring ready-made blocks and use the same API. You need the API itself for your own systems or integrations without a detour.
What does the API cost?
Nothing extra, included from Professional. All prices are provisional and net.
Goes well with
Zapier integrationHandovers in Slack, complaints in Sheets, orders as WhatsApp: over 7,000 apps, no code.
n8n integrationTalkward as a node in your own n8n. Triggers, actions and a tool for AI agents.
WhatsApp BusinessWhatsApp in the team inbox, with your own business account and your own number.
Critical alertsLoud alerts on the phone, even at night. Passed on to the next person until someone takes over. €5 per alert group.
MCP serverClaude, ChatGPT and your own agents read and work your inbox, with their own key per agent.- All integrationsShop, ERP, marketplaces, shipping and service
Secureyour seat.
Three details, no commitment. We will get back to you personally within two working days.