tawk.to API
Free live chat platform REST API for managing conversations, contacts, and chat history for customer support automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
API key only — no scopes or fine-grained access control. Key rotation not automated.
⚡ Reliability
Best When
Best for reading tawk.to chat history and managing contacts from backend automation workflows.
Avoid When
Avoid when you need to send messages or build chatbots via API — use tawk.to's JavaScript widget API instead.
Use Cases
- • Retrieve chat transcripts and conversation history for agent training data pipelines
- • Create and update contact records programmatically from CRM integration workflows
- • Build automated ticket routing by querying active chat conversations and agent availability
- • Extract customer support analytics (response times, conversation counts) for reporting agents
- • Automate pre-chat contact creation to pre-populate agent context before human handoff
Not For
- • Sending messages from the API — tawk.to REST API is read/management only, not send-message
- • Real-time bot automation within chat sessions — use tawk.to JavaScript API for in-widget automation
- • High-volume data exports — tawk.to throttles heavy API usage aggressively
Interface
Authentication
REST API uses API key (base64 encoded with colon prefix) in Authorization header. Property ID required in all requests.
Pricing
tawk.to is free forever for live chat. Revenue comes from hired agent services.
Agent Metadata
Known Gotchas
- ⚠ REST API is management-only — there is no API endpoint to send a chat message to a visitor
- ⚠ Property ID and Account ID are different identifiers — using the wrong one in API calls returns 404 or empty results
- ⚠ Rate limits are undocumented and silently enforced — implement 1-2 second delays between bulk requests to avoid throttling
- ⚠ Webhook events use different field names than REST API responses — don't assume schema parity between webhook payloads and API data
- ⚠ API documentation is sparse and outdated — test in Postman before relying on docs for field names and types
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for tawk.to API.
Scores are editorial opinions as of 2026-03-06.