Skip to main content
Every way of connecting an AI app to ChatSyncs needs your ChatSyncs API key. It is the one secret that proves the AI app is acting for your account. You get it once, from one place.

​
Find your key

1

Open the API Developer Console

Log in to ChatSyncs, then open the API Developer Console.
2

Copy the key

Your key is shown at the top of the page as Your API key. Copy all of it, and nothing else. A space picked up at the start or end is the most common reason a key is rejected.
3

Keep it handy for a minute

You paste it once, on the ChatSyncs connect page your AI app opens (or into your app’s settings, for the few apps that need it there). You don’t need to save it anywhere else.
The connect page has a Where do I find my API key? link that opens the same console page, so you can also grab the key at the moment you need it.

​
Keep it safe

Anyone holding your key can send WhatsApp messages from your number and read your contacts and conversations. Treat it like the password to your WhatsApp business.
  • Paste it only into the ChatSyncs connect page (its address starts with https://mcp.chatsyncs.com) or into your own AI app’s settings.
  • Never paste it into a chat with an AI, an email, a support ticket, a screenshot, or a shared document.
  • One key, whole account. There is no “limited” key. The key can do anything your ChatSyncs account can do through the API.

​
Where your key ends up

When you connect through the ChatSyncs connect page:
  1. ChatSyncs checks the key straight away, so a wrong key is caught on the spot.
  2. Your AI app receives a sealed, encrypted token that carries the key, and stores it in its own credential storage (on your computer, or in your account with that AI provider).
  3. The ChatSyncs MCP server keeps no copy and has no database of keys. Each request from your AI app brings the key with it; the server uses it for that request and forgets it.
For the few apps where you paste the key into a settings file instead (see each app’s page), the key sits in that file on your computer in plain text. Anyone who can open that file can read it, so don’t share or sync the file.

​
Revoke access: regenerate the key

Regenerating your key on the API Developer Console is the master off-switch. The new key replaces the old one, and every AI app still holding the old key stops working immediately, whichever app it is and wherever it is installed.

​
After you regenerate the key

Your apps won’t ask for the new key by themselves. They still look connected, but every ChatSyncs action fails with “ChatSyncs rejected the API key”. Reconnect each app you still want to use:
Removing ChatSyncs from one AI app is not the same as revoking the key. It deletes that app’s copy, which is enough for a tidy-up. If you think your key has been seen by someone else, or a device was lost, regenerate the key: that is the only step that cuts off every copy at once.

​
Frequently asked

Yes. It’s one key per account, used by the Developer API, by n8n or Make flows that call ChatSyncs, and by the MCP server. Regenerating it means updating every place that uses it, not just your AI apps.
No. A ChatSyncs key always carries the full permissions of the account. To limit what an AI app may do, use that app’s own controls: most let you set individual ChatSyncs abilities to “ask me first” or switch them off. See What the assistant can do.
A key belongs to a ChatSyncs account, not to a person. Anyone connecting with a key from your account acts as that account. Only share access with people you would trust with the account itself.
No. It stays valid until you regenerate it. Connected apps refresh their own access in the background, so you won’t be asked for the key again unless an app sits unused for more than a year. After a regenerate, you reconnect each app yourself (see above).