Log inStart Free Trial
easyCoexistence Official APIs

Is easyCoexistence safe? Security and data handling

Yes, easyCoexistence is safe to connect: it reaches each network only through that network's official API and sign-in, so no password is shared. It encrypts the tokens at rest with AES-256-GCM, renews them where the network allows, signs its events with X-EC-Signature and erases a connection's tokens on removal. Message text is kept only with automations or forwarding on: 7 days, or 30 in a run log.

  • Official APIs and the networks' own sign-in
  • Tokens encrypted at rest with AES-256-GCM
  • Signed events, and no message copies by default
Start Free Trial

Nothing charged for 3 days. Cancel anytime.

Official APIs onlyMCP for Claude and ChatGPTEvery connection monitored 24/73 days free
AES-256-GCM

The encryption easyCoexistence applies to the access tokens networks issue before it stores them.

7 days

How long message text is kept, only with automations or forwarding on; an automation's run log keeps it 30 days.

HMAC-SHA256

How X-EC-Signature signs each event: over the timestamp and raw body, with a secret shown once.

ec_live_

Prefix of the one Partner API key per account; only its hash is stored, and rotating ends the old key at once.

X-Hub-Signature-256

The header carrying the SHA256 signature Meta adds to webhook payloads, made with the subscribing app's secret.

Does easyCoexistence use official APIs?

Yes, and only those. Each connection runs on the network's official API and is authorized through the network's own sign-in: Meta's Embedded Signup for a WhatsApp number, and each social network's own OAuth consent screen for the rest. The owner approves the access there, so easyCoexistence never sees or stores a password for those accounts, and nothing logs in as the user.

easyCoexistence is an independent Meta Tech Provider, and WhatsApp numbers connect through Coexistence, Meta's own feature. The account bans people talk about hit unofficial tools that log in as the user, while a connected account follows its network's usual rules on what it sends, spam included.

How are access tokens kept?

Encrypted, renewed and shown only to the account they belong to. The tokens the networks issue are stored encrypted at rest with AES-256-GCM, easyCoexistence account passwords are hashed, and all traffic is served over HTTPS. Tokens are renewed before they lapse wherever the network allows it, so nobody has to paste one in again.

A connection's token goes only to the account it belongs to, through the MCP connector or the account's Partner API key, and a number's token also shows on its page in the dashboard. For a WhatsApp number it is the business's own token, scoped to its assets, and easyCoexistence's system token is never handed out. AI provider keys added for automations are encrypted too, and no tool returns them.

Does easyCoexistence store messages, comments or posts?

Not by default. A WhatsApp number's messages go from Meta to the endpoint set for it, and messages that reach easyCoexistence with no automation or forwarding on are dropped unread. Without an automation, comments, mentions and DMs from the social networks are processed in memory and passed on without a copy, and posts, comments and insights an AI agent reads go straight to it.

Turning on automations or forwarding changes that for the connection involved, so the flow can run. The table sets out what is kept and for how long:

What is keptFor how long
Access tokensEncrypted with AES-256-GCMUntil the connection is removed
WhatsApp message textOnly with automations or forwarding on7 days
Social comments and DMsOnly for an account with an automation on7 days
Automation runsEach step and its output30 days
Posts, comments and insights an AI readsNothingPassed straight to the assistant
Connection healthStatus, quality and a timeline of eventsWhile the account is active

How can your system tell an event came from easyCoexistence?

By its signature. Status events, forwarded social events and forwarded WhatsApp messages carry X-EC-Signature: t=<unix>,v1=<hex>, where v1 is the HMAC-SHA256 of the timestamp, a dot and the raw body, keyed with a secret that starts with whsec_ and is shown once. Status events use the account's secret, each social account its own, and each forwarding number its own.

Check it on the raw body, refuse a timestamp more than 5 minutes old and compare in constant time. Events are sent only to HTTPS addresses that resolve to public IPs, checked again at each delivery.

Check X-EC-Signature in Node.js
import crypto from "node:crypto";

// header: "t=1761900000,v1=5f2b…"; secret: whsec_…, shown once
export function isGenuine(rawBody, header, secret) {
  const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));
  const t = Number(parts.t);
  if (!t || Math.abs(Date.now() / 1000 - t) > 300) return false;
  const mac = crypto.createHmac("sha256", secret).update(parts.t + "." + rawBody).digest("hex");
  const given = String(parts.v1 ?? "");
  return given.length === mac.length && crypto.timingSafeEqual(Buffer.from(given), Buffer.from(mac));
}

How is the Partner API key protected?

It is shown once and stored only as a hash. Each account has one key, starting with ec_live_, made in the dashboard under Profile, Developers, or with the MCP tool create_api_key, and shown in full only at that moment. easyCoexistence keeps a SHA-256 hash to check requests, plus the first characters so the dashboard can show which key is live.

Rotating issues a new key and ends the old one at once, with no grace period, and revoking leaves the account with none. Repeated failed requests from one address are answered with 429 rather than 401, which keeps the key space from being probed. Keep the key on your server, never in front-end code.

How do you remove easyCoexistence's access?

From either side, at any time. Removing a number in the dashboard revokes easyCoexistence's access at Meta, deletes its token and stops monitoring it, while the WhatsApp Business app and its chats stay as they were. Removing a social account deletes its tokens and event settings, and on TikTok and YouTube also revokes the grant at the network. The Partner API does the same with DELETE /connections/:id and DELETE /channels/:id.

Owners can also remove the app in the network's own settings, which easyCoexistence detects. Deleting the connector in an AI assistant's settings ends that assistant's access, and deleting the account with its data can be requested by email.

Common mistakes

  • Checking a WhatsApp delivery's X-Hub-Signature-256 against your own Meta app secret. Meta signs those with the secret of easyCoexistence's app, which is never shared, so put a long random secret in the webhook URL instead.
  • Putting the Partner API key in front-end code. Anyone who opens the page could read it and fetch your customers' tokens with it, so keep it on your server.
  • Checking X-EC-Signature against JSON you parsed and serialized again. The signature covers the raw body byte for byte, so check it before parsing.
  • Creating the API key in a chat you share. create_api_key returns it in the conversation, where it stays, so rotate the key if that chat is shared.
Doing this with EasyCoexistence

easyCoexistence connects WhatsApp, Instagram, Facebook, TikTok, YouTube, LinkedIn and more channels only through each network's official API, keeps their tokens encrypted and renewed, stores no message content unless you turn on automations or forwarding, and watches every connection 24/7. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

Can my accounts get banned for connecting them to easyCoexistence?

Not for connecting them: each runs on the network's official API, which is what the networks provide for this. An account can still be limited for what it sends, such as spam, just as it could be from the network's own app.

Does easyCoexistence read my customers' messages?

Only for a connection where you turn on automations or forwarding, so the flow can run, and the text is then kept for 7 days, or 30 in the log of an automation run it started. Otherwise a message goes to your endpoint, or is dropped unread.

Who can see a connection's access token?

Only the account it belongs to, through the MCP connector or its Partner API key, plus a number's own page in the dashboard. Your own code should fetch it when needed rather than keep a copy.

How do I delete my data?

Remove the connections in the dashboard, which deletes their tokens, then email the contact on the privacy policy to delete the account. That removes the account, its connections, stored tokens and monitoring history.

Keep reading

Connect your first channel in two minutes.

No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.

  • 3 days free
  • Cancel any time
  • Official APIs only
  • Monitored 24/7

Verified on