tawk.to
Connect tawk.to to manage live chat agents, chats, tickets, members, chat widgets, and knowledge base articles.
You end up pasting a single tawk.to REST API key, created under your profile's REST API Keys tab once tawk.to approves your beta access request.
Partner application before this connector works
tawk.to's REST API is not self-serve: it is available by request only, and you must be approved through tawk.to's REST API Beta access request form before the REST API Keys screen appears in your account.
- Typical wait
- Not published. tawk.to states only that once the request is approved you receive a username, password and a link to the REST API documentation; no SLA or turnaround figure is given on either the help article or the request form.
- Cost
- No charge is stated. Neither the REST API help article nor the beta access request form names a fee or a plan requirement, and tawk.to publishes no API pricing.
- Blocked until approved
- Everything on the REST API: listing properties, reading and managing conversations, agents, tickets and knowledge base entries. Until approval you cannot even generate a key - the 'REST API Keys' item does not appear under Edit Profile, and the API documentation URL is only sent to approved requesters.
- Works meanwhile
- The tawk.to JavaScript API (Tawk_API) works immediately on any account with no approval - widget control, visitor attributes, tags, and event hooks such as onChatStarted/onChatEnded. Webhooks configured per property in Administration also work without applying, so inbound event-driven integrations can be built while you wait.
Where to apply: Submit the form at https://www.tawk.to/rest-api-beta-access-request/. After approval, go to your dashboard, click your profile image (top right) > Edit Profile > REST API Keys > Create Key. Existing tawk.to partners can instead ask their account representative.
- It is a beta/partner programme, not a self-serve console - a plausible business use case in the form matters more than technical detail.
- Approval is granted per account, so a key issued to one tawk.to account does not cover another workspace you administer.
- Do not confuse the JavaScript API (public, documented at developer.tawk.to) with the REST API - the public developer portal documents only the former, which is why people assume the REST API is open.
- Setup time
- 5 min, after tawk.to approves your access request
- Auth
- API credentials
- API base URL
- https://api.tawk.to/v1
- Rate limits
- tawk.to does not publish REST API rate limits. Their guidance is to plan for retries with backoff in case of temporary errors.
Before you begin
- A tawk.to account (the REST API is free, but gated)
- REST API beta access approved by tawk.to. You submit a request form and wait for a manual approval email
- Desktop or laptop browser. tawk.to says the REST API Keys screen is not available in the mobile apps
- The tawk.to email address of the user who will hold the key (asked for on the request form)
Get your credentials
Request REST API beta access
Open the REST API Access Request Form and fill in the tawk.to email address of the user requiring access. Pick Internal purposes or To build a publicly available integration, then click Request access.
REST API Beta
Request access to the tawk.to REST API.
Approval arrives by email with a username, a password and a link to the REST API documentation.
Open Edit Profile in the dashboard
Sign in at dashboard.tawk.to and click your profile image in the lower-left corner. Click Edit Profile.
Monitoring
Live visitors on acme-supply.com.
| Visitor | Page | Status | Time on site |
|---|---|---|---|
| Visitor 4821Sydney, AU | /pricing | Chatting | 4m 12s |
| Visitor 4822Auckland, NZ | /docs/api | Browsing | 1m 03s |
The avatar menu opens upward from the bottom-left corner of the dashboard.
Create a key under REST API Keys
In Account Settings, click REST API Keys in the left menu. Click Create Key.
REST API Keys
Keys that authenticate REST calls as this agent.
| Key | Created | Last used | Status |
|---|---|---|---|
| 3f2a****9c14Created by Alex Rivera | Mar 4, 2026 | Mar 6, 2026 | Active |
| b71d****04aeCreated by Dana R. | Nov 18, 2025 | Never | Unused |
Select a key and click Delete to revoke it.
Copy the key into PopMCP
Copy the new key from the list. Paste it into the REST API key field on the PopMCP tawk.to connect form.
REST API Keys
- Auth scheme
- HTTP Basic
- Username
- 3f2a****9c14
- Password
- (empty)
- Base URL
- https://api.tawk.to/v1/
There is no client id and no secret. tawk.to issues one value.
Connect in PopMCP
Open your workspace, choose tawk.to in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| REST API keysecret | First request REST API access at help.tawk.to/article/rest-api (approved in ~24–48h). Then in tawk.to go to Profile → Edit Profile → REST API Keys → Create Key and paste the key here. Sent as HTTP Basic auth (key as username, empty password) and stored encrypted; used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against tawk.to immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows tawk.to as Connected and the agent, chat, ticket, property-member, widget and Knowledge Base tools appear. Under the hood PopMCP calls POST https://api.tawk.to/v1/agent.me and gets back your agent record.
Troubleshooting
There is no REST API Keys tab in Account Settings
Why: Your account has not been granted REST API beta access, or you are signed in as a different tawk.to user than the one named on the request form.
Fix: Re-check the approval email, sign in as the exact tawk.to email you listed on the request form, or submit the REST API Access Request Form again at https://www.tawk.to/rest-api-beta-access-request/.
401 Unauthorized on every call
Why: The key was deleted, or it is being sent as a bearer token instead of HTTP Basic with the key as the username.
Fix: Confirm the key still exists in REST API Keys and re-paste it into PopMCP. PopMCP handles the Basic auth encoding, so paste the raw key with no 'Bearer' prefix and no trailing spaces.
Calls work for one website but not another
Why: tawk.to scopes data by property, and the key inherits the properties of the agent who created it.
Fix: Add that agent as a Property Member on the missing property, or create the key from an account that is a member of every property you need.
The REST API Keys screen will not open on mobile
Why: tawk.to documents the REST API key flow as desktop and laptop only.
Fix: Open dashboard.tawk.to in a desktop browser.
The key stops working after an agent leaves
Why: A key inherits the permissions of the agent who created it, so removing that agent removes the key's access.
Fix: Create the key from a long-lived admin account rather than an individual agent's account, then re-paste the new key into PopMCP.