# tawk.to setup for PopMCP 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. - Auth: API credentials - Setup time: 5 min, after tawk.to approves your access request - API base URL: https://api.tawk.to/v1 - Credentials screen: https://dashboard.tawk.to/ - Provider docs: https://help.tawk.to/article/rest-api ## Approval required before this 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. ## 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 ### 1. 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. Screen: https://www.tawk.to/rest-api-beta-access-request/ ### 2. 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. Screen: https://dashboard.tawk.to/ ### 3. Create a key under REST API Keys In Account Settings, click REST API Keys in the left menu. Click Create Key. ### 4. 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. ## Fields PopMCP asks for - REST API key (apiKey) [required]: 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. ## Verify 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 Cause: 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 Cause: 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 Cause: 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 Cause: 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 Cause: 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. --- Source: https://www.docs.popmcp.com/docs/integrations/tawk/