文档

什么是 EasyCoexistence？

EasyCoexistence 会通过 Meta 的官方 Coexistence 功能，将您已经在 WhatsApp Business Platform（Cloud API）上使用的企业号码连接起来，然后全天候监控连接状态，避免连接在没有提示的情况下中断。

• 您手机上的应用会照常运行。Coexistence 会在旁边加入 API，不会替换任何内容。
• 无需迁移，也不会丢失聊天记录：您的历史记录仍保留在手机上。
• 您可以在同一个账户中连接任意数量的号码。
• 您的对话不会经过我们的服务器。Meta 可以直接将收到的消息路由到您自己的系统。

连接号码

1. 创建您的账户并打开控制台。
2. 点击“连接号码”。Meta 的窗口会打开；使用管理您企业的 Facebook 账户登录。
3. 输入您的企业号码，然后使用手机上的 WhatsApp Business 应用扫描二维码。
4. 完成，通常不到 2 分钟。该号码会显示在您的控制台中，并附带实时连接状态。

您的号码符合条件吗？先阅读这里

Meta 在允许使用 Coexistence 之前会执行几项规则检查。大多数连接失败都属于以下其中一种情况：

• 号码必须在版本 2.24.17 或更高版本的 WhatsApp Business 应用中使用。个人 WhatsApp 账户无法连接。
• 号码需要有真实且近期的双向对话活动。全新或长期闲置的号码会被拒绝。
• 号码不能连接到其他 API 平台或服务提供商（群发工具、CRM、自动化工具）。请先在那里断开连接，然后再试。
• 应用中的两步验证或待处理的设备配对，也可能阻止注册。

如果 Meta 显示“已注册到现有 WhatsApp 账户”，请不要删除手机上的 WhatsApp 账户；号码必须继续在应用中保持启用。请改为从其他平台解除连接。

应用会发生哪些变化（需要权衡的地方）

启用 Coexistence 后，应用的几项功能会被停用，而且全部只影响一对一聊天。连接前请了解这些变化：

• 一对一聊天中的消息自动消失功能会被关闭。
• 一对一聊天中的阅后即焚消息会被停用。
• 一对一聊天中的实时位置分享会被停用。
• 广播列表：您无法创建新的广播列表，现有列表会变为只读。
• 注册时，所有已连接的设备都会断开，需要重新连接。Windows 版 WhatsApp 和 WearOS 将不再受支持。
• 群组、通话、目录和状态仍可在应用中使用，但不会显示在 API 端。
• 号码的 API 吞吐量上限为每秒 20 条消息。日常聊天不受影响。

通过您的 AI 使用它（每个账户一个连接器）

您的整个账户会获得一个连接器 URL。它适用于您现在和将来连接的每个号码：您的 AI 可以看到所有号码，并为每项任务选择正确的号码。

• Claude（网页或桌面版）：设置 → 连接器 → 添加自定义连接器，然后粘贴 URL。
• ChatGPT：设置 → 连接器 → 高级，启用开发者模式，然后添加 URL。
• Claude Code（终端）：claude mcp add --transport http easycoexistence https://easycoexistence.com/api/mcp
• 系统提示时，使用您的 EasyCoexistence 电子邮件和密码登录，并授权访问。

然后直接询问：“从我的号码发送消息”、“创建促销消息模板”、“我的号码连接状态良好吗？”、“将收到的消息路由到我的系统”。

您的 AI 可以做什么（工具）

• list_numbers：列出您的所有号码，以及状态、质量和级别。
• get_number_health：显示来自 Meta 的实时快照，以及近期事件时间线。
• send_message：在 24 小时服务窗口内发送自由格式回复。
• create_template、get_template_status、list_templates：创建和跟踪消息模板。
• send_template：使用已批准的模板开始对话。
• get_api_credentials：获取用于连接您自己系统的 ID、端点和访问令牌。
• set_webhook_destination：将收到的消息直接从 Meta 路由到您的 Webhook。
• get_connect_link：了解如何注册另一个号码。
• get_docs：获取本文档，让您的 AI 可以回答有关产品的问题。

发送规则（由 Meta 设定，不是我们设定）

• 回复可以自由编写：任何在过去 24 小时内给您发过消息的人，都可以直接回复。
• 开始对话需要使用预先批准的消息模板。
• 在 Coexistence 中，模板只能通过 API 发送；手机应用无法发送模板。
• 营销消息由 Meta 通过您自己的 WhatsApp Business Account 付款方式计费。我们不会在消息费用上加价。
• Meta 会限制 Coexistence 号码的 API 吞吐量；手机上的日常消息不受影响。

接入您自己的系统

控制台中每个号码的页面都会显示 API 基础 URL、账户 ID、电话号码 ID 和访问令牌：这些正是 n8n、CRM 或自定义代码通过官方 Cloud API 发送消息所需的全部信息。要接收消息，请让您的 AI 将收到的消息路由到您的 Webhook（set_webhook_destination）：然后 Meta 会直接将消息发送到您的端点，不会经过我们的服务器。

监控与 14 天规则

我们通过 Meta Webhook 和定期检查，全天候监控每个已连接号码（连接状态、质量评级和消息级别）。如果手机上的企业应用大约 14 天没有打开，Meta 可能会在没有提示的情况下断开 Coexistence 连接。一旦发生任何问题，您的控制台会显示原因。经验法则：像平常一样继续使用该应用。

EasyCoexistence 不是什么

• 不是收件箱，也不是聊天机器人。对话仍会在您的应用、AI 或您自己的系统中进行；我们不会增加另一个需要长期使用的面板。
• 不是群发消息工具。Meta 的规则仍然适用：在 24 小时窗口内回复，开始对话时使用模板。
• 不是 Meta 的产品。我们是独立的 Tech Provider，使用平台的官方 Coexistence 功能。
• 不是您消息的中间人。我们绝不会读取或存储您对话的内容。

即使 EasyCoexistence 明天停止服务，也不会影响您的号码：应用会继续运行，历史记录仍保留在手机上，而且 API 连接随时可以撤销。这是一座桥梁，不是牢笼。

常见问题

指南

所有其他页面都会指向这里的详细说明。

• WhatsApp MCP server for Claude, ChatGPT and CursorConnect Claude, ChatGPT or Cursor to a real WhatsApp number over MCP. Official Cloud API, eleven tools, no linked-device workaround and no ban risk.
• WhatsApp Coexistence: the app and the API on one numberCoexistence runs the WhatsApp Business app and the Cloud API on the same number at once. What it changes, what it does not, and how a number gets connected.
• Unofficial WhatsApp APIs: what actually gets numbers bannedUnofficial WhatsApp gateways sign in as a linked device, which breaks Meta's terms. What that costs, and what the official route looks like instead.
• WhatsApp Cloud API or Coexistence: which one a number needsBoth are Meta's. One takes the number onto the API alone, the other runs the API beside the WhatsApp Business app. Which to pick, and what each costs you.
• WhatsApp webhooks: routing messages straight to your serverHow WhatsApp webhooks work, what Meta sends, and how to route incoming messages directly to your own endpoint instead of through a provider's platform.
• WhatsApp Coexistence for agencies and consultanciesConnect client WhatsApp numbers without migrating them or retraining their staff. One account, many numbers, each in the client's own Business Portfolio.
• What being a Meta Tech Provider means, and why it mattersA Tech Provider connects other businesses' WhatsApp numbers through its own Meta app. What the status requires, and what it changes for the client.
• What WhatsApp Coexistence costs, provider by providerWhat each provider charges to hold WhatsApp numbers, at one, ten and fifty numbers. Figures from their own pricing pages, September 2026.
• WhatsApp Coexistence glossaryPlain definitions for the vocabulary around WhatsApp Coexistence: WABA, Business Portfolio, phone number id, templates, quality rating, Tech Provider and MCP.
• Can you use the WhatsApp Business app and the API on the same number?Yes. Coexistence is Meta's official feature for running the WhatsApp Business app and the Cloud API on one number at once. How it works and what changes.
• How to connect WhatsApp to an API without losing your chatsConnecting a WhatsApp Business number to the Cloud API without losing conversations. Why chats stay on the phone and what actually syncs.
• The cheapest way to get the WhatsApp Business APIWhat the WhatsApp Business API actually costs: Meta's conversation fees versus provider fees, and how to pay the least.

集成

通过您已经在使用的工具访问已连接的号码。

• Connect WhatsApp to n8n on the official Cloud APIRoute WhatsApp messages into an n8n workflow over Meta's official Cloud API, on a number the business still answers from the phone. No linked device.
• Connect WhatsApp to Claude with a custom connectorAdd EasyCoexistence as a custom connector and Claude can read, send and wire a real WhatsApp number over Meta's official Cloud API. One OAuth sign in.
• Connect WhatsApp to Make on the official Cloud APIRoute WhatsApp messages into a Make scenario over Meta's official Cloud API. Why Make uses the webhook path rather than our MCP server.
• Connect WhatsApp to Zapier on the official Cloud APITrigger a Zap from an incoming WhatsApp message over Meta's official Cloud API, and send replies back with a webhook action.
• Connect WhatsApp to ChatGPT with a custom connectorAdd EasyCoexistence as a connector in ChatGPT and it can read, send and wire a real WhatsApp number over Meta's official Cloud API.
• Connect WhatsApp to Cursor over MCPAdd EasyCoexistence to Cursor's MCP settings and send WhatsApp messages, manage templates and wire webhooks without leaving the editor.
• Connect WhatsApp to Claude Code over MCPOne command adds EasyCoexistence to Claude Code, so an agent can send WhatsApp messages, manage templates and wire webhooks from the terminal.
• Send and receive WhatsApp from PythonReceive WhatsApp messages in a Python web handler and send replies through Meta's official Cloud API, on a number a team still answers from the phone.
• Send and receive WhatsApp from Node.jsReceive WhatsApp messages in a Node handler and send replies through Meta's official Cloud API, on a number a team still answers from the phone.

比较

人们在选择之前会权衡的因素。

• EasyCoexistence vs a BSP inboxA BSP gives you a shared inbox and sits in the message path. Coexistence keeps the phone and routes messages to your own systems. When each one is right.
• EasyCoexistence vs building it yourselfEverything here is Meta's documented API, so you can build it. What that actually takes, and the part that is not the building.
• EasyCoexistence vs 360dialogBoth charge per number and neither marks up Meta's fees. The difference is the price and what the fee is for. Prices as published in September 2026.
• EasyCoexistence vs WATIWati is a WhatsApp inbox priced per seat with contact limits. EasyCoexistence charges per connected number and routes messages to your own system.
• EasyCoexistence vs respond.ioRespond.io is a multichannel inbox priced per seat and contact. EasyCoexistence charges per connected number, with no seats and nothing per message.
• EasyCoexistence vs DualhookBoth route WhatsApp webhooks directly from Meta and neither stores messages. Where they differ on price, tooling and what survives a reconnection.
• EasyCoexistence vs AiSensyAiSensy is a WhatsApp campaign platform sold on monthly plans. EasyCoexistence charges per connected number and delivers messages to your own system.
• EasyCoexistence vs InteraktInterakt is a WhatsApp commerce platform with per-agent plans. EasyCoexistence charges per connected number, with no seats and nothing per message.
• EasyCoexistence vs DoubleTickDoubleTick is a WhatsApp sales inbox priced per user. EasyCoexistence charges per connected number and routes messages into the CRM you already use.
• EasyCoexistence vs ZokoZoko is a WhatsApp commerce platform built for Shopify. EasyCoexistence is the layer underneath, charging per connected number with no seats.
• EasyCoexistence vs TrengoTrengo is a multichannel team inbox priced per user. EasyCoexistence charges per connected number and delivers WhatsApp to your existing helpdesk.
• EasyCoexistence vs RasayelRasayel is a WhatsApp sales inbox priced per user. EasyCoexistence delivers the conversation straight into your CRM, charging per connected number.
• EasyCoexistence vs CallbellCallbell is a small-team WhatsApp inbox priced per user. EasyCoexistence charges per connected number, so headcount never enters the bill.
• EasyCoexistence vs BaileysBaileys is an open-source linked-device library, which breaches WhatsApp's terms. EasyCoexistence connects the same number through Meta's own API.
• EasyCoexistence vs WPPConnectWPPConnect automates WhatsApp Web in a browser session, against WhatsApp's terms. EasyCoexistence uses Meta's official Cloud API through Coexistence.
• EasyCoexistence vs Evolution APIEvolution API wraps unofficial WhatsApp libraries behind a REST interface. EasyCoexistence uses Meta's official Cloud API, so the number cannot be banned.
• EasyCoexistence vs WhapiWhapi is a hosted unofficial gateway, so the number is reached outside Meta's API. EasyCoexistence connects it officially through Coexistence.
• The best WhatsApp Coexistence providersEvery provider that supports WhatsApp Coexistence, what each charges and who each suits. Prices from their own published pages, September 2026.
• The best WhatsApp Cloud API providersWhatsApp Cloud API providers compared by how they charge: per message, per seat, or per number. Prices from their own published pages.
• The best WhatsApp MCP serversWhatsApp MCP servers compared. Most open-source ones drive an unofficial bridge that risks a ban. EasyCoexistence runs on Meta's official Cloud API.
• EasyCoexistence vs TwilioTwilio adds a published per-message fee on top of Meta's. EasyCoexistence charges a flat monthly fee per number and never touches the message bill.
• EasyCoexistence vs GupshupGupshup publishes a per-message fee on top of Meta's. EasyCoexistence charges per number, so the cost stops moving once the number is connected.
• EasyCoexistence vs InfobipInfobip is enterprise CPaaS priced per country through sales. EasyCoexistence publishes one price list and connects a number in minutes.
• EasyCoexistence vs YCloudBoth support Coexistence with no per-message markup. YCloud sells a platform in seat-based tiers; EasyCoexistence sells infrastructure per number.
• EasyCoexistence vs SleekFlowSleekFlow is a seat-priced messaging platform with a minimum seat count. EasyCoexistence charges per connected number with no seats at all.
• EasyCoexistence vs BirdBird quotes one blended per-message rate with Meta's fee inside it. EasyCoexistence charges per number and leaves the Meta invoice untouched.
• EasyCoexistence vs ZenviaZenvia sells monthly software plans plus channel packages. EasyCoexistence charges one published fee per connected number, in reais or dollars.
• EasyCoexistence vs 8x88x8 is enterprise CPaaS with good Coexistence documentation. EasyCoexistence is the self-serve product that does what those docs describe.

开始使用

连接号码，以及接下来会发生什么。

• Coexistence referenceWhat Coexistence is, how messages flow, what it costs, what it cannot do, eligibility, and how to roll it back. The short reference version.
• Connecting a number, step by stepWhat happens when you connect a number through Coexistence, what the business owner has to do, and what is decided once and cannot be changed.
• Which WhatsApp features stop working after CoexistenceDisappearing messages, view once, live location and broadcast lists are switched off on a connected number. What each one means in practice.
• Which numbers are eligible for CoexistenceThe app version, the account type, the portfolio access, and what actually makes Meta refuse a number during Coexistence onboarding.
• Rate limits and messaging throughputThe four separate WhatsApp Cloud API limits: messaging tier, throughput, per-recipient pairing and management calls.
• A number stopped working: how to find out whyA checklist in the order these failures actually happen: token, webhook override, inactivity disconnection, quality, and account restriction.
• What changes in the WhatsApp Business app after connectingEverything that stays the same on the phone after a number is connected through Coexistence, and the three things that genuinely change.
• What syncs to the API, and what does notContacts and one-to-one history cross over. Groups, catalog, labels, quick replies and away messages do not. The complete list, in one place.

Meta 平台

每个号码背后的账户、标识符和验证步骤。

• Display names on a WhatsApp business numberThe name customers see above a conversation. How approval works, what gets rejected, and which webhook reports the decision.
• Meta Business Portfolio, and what sits inside itThe company level container in Meta Business Manager. What it holds, why it matters for a client's number, and how it differs from a WABA.
• Two step verification on a WhatsApp numberThe six digit PIN set on a WhatsApp Business number, which operations require it, and what to do when nobody remembers it.
• The WhatsApp Business Account, and why overrides live on itWhat a WABA holds, why webhook overrides are applied at this level rather than per number, and what that means when a connection is removed.

发送消息

可以发送什么、何时发送，以及 Meta 首先会审核什么。

• The 24 hour customer service windowWhat the customer service window is, when it opens and closes, what may be sent inside and outside it, and why replies inside it are free.
• Which WhatsApp conversations Meta charges forReplies inside the customer service window are free. What Meta charges for, who it bills, and why a provider cannot mark it up.
• Message reactions: sending and receiving emojiSending and receiving WhatsApp message reactions through the Cloud API, including how a removed reaction arrives.
• WhatsApp message templatesWhat templates are, the three categories, how variables work, how review goes, and why on Coexistence they can only be sent through the API.
• Sending a template with variablesHow to fill WhatsApp template variables correctly: positional parameters, component lists, and the errors each mistake produces.
• Sending interactive messages: buttons and listsWhatsApp interactive messages: reply buttons, list messages, their exact limits and how replies come back on your webhook.
• Sending location and contact messagesSending location pins and contact cards through the WhatsApp Cloud API, and why live location is unavailable on a Coexistence number.
• Sending media: images, video, audio and documentsSending images, video, audio and documents on the WhatsApp Cloud API: size limits, supported formats, and why uploading beats linking.
• Template categories: utility, marketing and authenticationThe three template categories, what belongs in each, how they differ on billing and review, and why the wrong category is a reliable rejection.
• Template components: header, body, footer and buttonsThe four parts of a WhatsApp message template, what each one allows, and which of them accept variables.
• The template status lifecycleEvery state a WhatsApp template passes through, from submission to permanent disabling, and which webhook reports each one.

Webhook

事件如何到达您的系统，以及事件包含哪些内容。

• The account_alerts webhookMeta's general alerting channel for a business account. What arrives here, and why it is a prompt to look rather than a state change.
• The account_review_update webhookMeta reports the outcome of an account review here. What the decision field carries, and why a rejection is worth treating as a degraded connection.
• The account_update webhook, and every disconnection reasonaccount_update reports connection state changes. The full list of disconnection reasons Meta sends, what each means, and which ones are recoverable.
• The business_capability_update webhookHow messaging limit changes arrive. What the tier means, why it moves in both directions, and how it differs from throughput.
• WhatsApp webhook fields, and which ones go whereThe eight webhook fields a Coexistence connection uses, what each carries, and which are routed to your endpoint versus kept for monitoring.
• The history webhookThe one time chat history transfer on a Coexistence number is delivered on this field. What arrives, when, and why it happens only once.
• The message_template_quality_update webhookMeta reports a template's quality moving here, before it results in a pause. What the signal means and why it is worth acting on early.
• The message_template_status_update webhookMeta reports template approvals, rejections and disabling here. What each status means and why it removes the need to poll.
• The messages webhookEverything a customer sends arrives on this field. What the payload carries, how to acknowledge it, and why it never reaches a provider on a routed number.
• The phone_number_name_update webhookMeta reports display name approvals and rejections here. It is the only place the decision appears, and nothing shows it in the app.
• The phone_number_quality_update webhookWhat this webhook actually carries as of 2026, why the colour quality rating is not in it, and where the rating has to be read from instead.
• The smb_app_state_sync webhookContact synchronisation from the WhatsApp Business app arrives on this field. What it carries and why it is separate from message history.
• The smb_message_echoes webhookHow software sees what a human sent from the WhatsApp Business app. Only exists on Coexistence numbers, and ignoring it causes double replies.
• The template_category_update webhookMeta can move a template between utility, marketing and authentication after approval. This reports it, and it changes what each send costs.
• Verifying a WhatsApp webhook endpointMeta calls your endpoint with a GET challenge before delivering anything. What it sends, what to return, and why a wrong answer fails silently.

MCP 连接器

通过 AI 助手访问号码。

• MCP or a webhook: which one you actually needMCP acts when asked. A webhook reacts when something happens. Why an assistant cannot answer customers on its own, and why most systems need both.
• MCP tools referenceAll eleven tools the EasyCoexistence MCP connector exposes, what each takes, and which are gated when billing lapses.

错误代码

用户实际遇到的所有错误，均来自 Meta 发布的参考资料。

• 100invalid parameter
• 190access token expired
• 368account restricted by policy
• 80007rate limit on the WhatsApp Business Account
• 130429throughput limit reached
• 130497recipient country not allowed
• 131000something went wrong
• 131008required parameter missing
• 131009invalid parameter value
• 131016service unavailable
• 131021sender and recipient are the same
• 131026message undeliverable
• 131031account restricted or data mismatch
• 131042business account payment issue
• 131045phone number not registered
• 131047re-engagement message
• 131048spam rate limit hit
• 131049message blocked for ecosystem health
• 131050the user has opted out
• 131051unsupported message type
• 131052media download failed
• 131053media upload failed
• 131056too many messages to one recipient
• 132000parameter count mismatch
• 132001template does not exist
• 132007template policy violation
• 132012template parameter format mismatch
• 132015template paused for quality
• 132016template is permanently disabled
• 133005incorrect two-step verification PIN
• 133006phone number not verified
• 133008too many PIN guesses
• 133010phone number not registered
• 2593107synchronization limit exceeded
• 2593108sync outside the 24 hour window
• codesWhatsApp Cloud API error codes

支持

如果这里没有回答您的问题，请写信给 matheus@tonelotto.com.