Dokumentasyon
Lahat tungkol sa pag-connect ng inyong numero, pagpapanatiling maayos ng koneksyon, at paggamit nito mula sa inyong AI o sariling system.
Ano ang EasyCoexistence?
Inilalagay ng EasyCoexistence ang business number na ginagamit na ninyo sa WhatsApp Business Platform (Cloud API) gamit ang opisyal na Coexistence feature ng Meta, pagkatapos ay mino-monitor ang koneksyon nang buong araw at gabi para hindi ito biglang mawala nang hindi ninyo nalalaman.
- Patuloy na gagana ang app sa inyong phone gaya ng dati. Idinadagdag lang ng Coexistence ang API, at walang pinapalitan.
- Walang migration at walang nawawalang chat: nananatili ang inyong history sa phone ninyo.
- Mag-connect ng kahit ilang numero sa iisang account.
- Hindi dumadaan sa aming servers ang inyong mga conversation. Maaaring direktang i-route ng Meta ang mga incoming message sa sarili ninyong system.
Pag-connect ng numero
- Gumawa ng inyong account at buksan ang dashboard.
- I-click ang “Ikonekta ang isang numero”. Magbubukas ang window ng Meta; mag-log in gamit ang Facebook account na namamahala sa inyong negosyo.
- Ilagay ang inyong business number at i-scan ang QR code gamit ang WhatsApp Business app sa inyong phone.
- Tapos na, karaniwan sa loob ng wala pang 2 minuto. Lalabas ang numero sa inyong dashboard kasama ang live na health status.
Eligible ba ang inyong numero? Basahin muna ito
Nagpapatupad ang Meta ng ilang rule bago payagan ang Coexistence. Karamihan sa mga nabigong koneksyon ay dahil sa isa sa mga ito:
- Dapat nasa WhatsApp Business app ang numero, bersyon 2.24.17 o mas bago. Hindi maaaring i-connect ang mga personal na WhatsApp account.
- Kailangan ng numero ng tunay at kamakailang two-way conversation activity. Tinatanggihan ang mga bagong gawa o hindi aktibong numero.
- Hindi maaaring naka-attach ang numero sa isa pang API platform o provider (bulk senders, CRM, automation tools). I-disconnect muna ito roon, pagkatapos ay subukan muli.
- Maaari ring humarang sa onboarding ang two-step verification o may nakabinbing device pairing sa app.
Kung sabihin ng Meta na “registered to an existing WhatsApp account” ang numero, HUWAG ninyong i-delete ang WhatsApp account sa phone ninyo; dapat manatiling active ang numero sa app. I-free ito mula sa kabilang platform.
Ano ang nagbabago sa app (ang mga trade-off)
Kapag in-on ang Coexistence, madi-disable ang ilang feature ng app, at lahat ng ito ay sa mga individual (1:1) chat. Alamin muna ang mga ito bago mag-connect:
- Naka-off ang disappearing messages sa 1:1 chat.
- Naka-disable ang view-once messages sa 1:1 chat.
- Naka-disable ang live location sharing sa 1:1 chat.
- Broadcast lists: hindi na kayo makakagawa ng bago, at magiging read-only ang mga dati na.
- Sa onboarding, madi-disconnect ang lahat ng linked device at kailangan itong i-re-link. Hindi na susuportahan ang WhatsApp for Windows at WearOS.
- Patuloy na gagana sa app ang groups, calls, catalog at status, pero hindi lalabas ang mga ito sa API side.
- Magkakaroon ang numero ng pinagsamang API throughput cap na 20 mensahe bawat segundo. Hindi maaapektuhan ang pang-araw-araw na pagcha-chat.
Gamitin ito mula sa inyong AI (isang connector bawat account)
May iisang connector URL ang buong account ninyo. Gumagana ito para sa bawat numerong i-connect ninyo, kasalukuyan man o sa hinaharap: nakikita ng inyong AI ang lahat ng numero ninyo at pinipili ang tama para sa bawat task.
- Claude (web o desktop): Settings → Connectors → Add custom connector, pagkatapos ay i-paste ang URL.
- ChatGPT: Settings → Connectors → Advanced, i-enable ang Developer mode, pagkatapos ay idagdag ang URL.
- Claude Code (terminal): claude mcp add --transport http easycoexistence https://easycoexistence.com/api/mcp
- Kapag hiniling, mag-log in gamit ang inyong EasyCoexistence email at password at pahintulutan ang access.
Pagkatapos, itanong lang: “mag-send ng mensahe mula sa numero ko”, “gumawa ng promo template”, “healthy ba ang numero ko?”, “i-route ang incoming messages sa system ko”.
Ano ang kayang gawin ng inyong AI (tools)
- list_numbers: lahat ng numero ninyo kasama ang status, quality at tier.
- get_number_health: live snapshot mula sa Meta kasama ang kamakailang event timeline.
- send_message: free-form reply sa loob ng 24-hour service window.
- create_template, get_template_status, list_templates: gumawa at subaybayan ang mga message template.
- send_template: simulan ang mga conversation gamit ang approved template.
- get_api_credentials: mga ID, endpoint at token para maikonekta ang sarili ninyong system.
- set_webhook_destination: direktang i-route mula sa Meta ang incoming messages sa inyong webhook.
- get_connect_link: kung paano mag-onboard ng isa pang numero.
- get_docs: dokumentasyong ito, para masagot ng inyong AI ang mga tanong tungkol sa product.
Mga rule sa pagpapadala (itinatakda ng Meta, hindi namin)
- Free-form ang pagre-reply: maaaring direktang sagutin ang sinumang nag-message sa inyo sa loob ng nakaraang 24 oras.
- Kailangan ng pre-approved template para magsimula ng conversation.
- Sa Coexistence, sa pamamagitan lang ng API maaaring mag-send ng templates; hindi ito maipapadala ng phone app.
- Sisingilin ng Meta ang marketing messages sa payment method ng sarili ninyong WhatsApp Business Account. Hindi kami naglalagay ng markup sa messaging.
- Nililimitahan ng Meta ang API throughput para sa mga Coexistence number; hindi maaapektuhan ang pang-araw-araw na messaging sa phone.
I-connect ang sarili ninyong system
Ipinapakita sa page ng bawat numero sa dashboard ang API base URL nito, account at phone ID, at access token: lahat ng kailangan ng n8n, CRM o custom code para mag-send gamit ang opisyal na Cloud API. Para makatanggap, hilingin sa inyong AI na i-route ang incoming messages sa inyong webhook (set_webhook_destination): pagkatapos ay direktang ihahatid ng Meta ang mga ito sa inyong endpoint, at hindi kailanman dadaan sa aming servers.
Monitoring at ang 14-day rule
Binabantayan namin nang buong araw at gabi ang bawat naka-connect na numero (connection state, quality rating at messaging tier) gamit ang Meta webhooks at pana-panahong checks. Kung humigit-kumulang 14 na araw na hindi nabubuksan ang business app sa phone, maaaring tahimik na alisin ng Meta ang Coexistence link. Sa sandaling may masira, ipapakita ito ng inyong dashboard kasama ang dahilan. Simpleng rule: patuloy na gamitin ang app gaya ng dati.
Ano ang hindi EasyCoexistence
- Hindi ito inbox o chatbot. Patuloy na nangyayari ang mga conversation sa inyong app, inyong AI o sarili ninyong system; hindi kami nagdadagdag ng isa pang panel na kailangan ninyong gamitin.
- Hindi ito mass-messaging tool. Patuloy na umiiral ang mga rule ng Meta: replies sa loob ng 24-hour window at templates para magsimula ng conversation.
- Hindi ito produkto ng Meta. Isa kaming independent Tech Provider na gumagamit ng Coexistence, ang opisyal na feature ng platform.
- Hindi kami middleman para sa inyong messages. Hindi namin kailanman binabasa o sini-store ang content ng inyong conversations.
At kung mawala ang EasyCoexistence bukas? Walang mangyayari sa inyong numero: patuloy na gagana ang app, mananatili ang history sa phone ninyo, at maaaring i-undo anumang oras ang API connection. Isang tulay, hindi kulungan.
Mga karaniwang tanong
Magkano ang halaga?
Depende ito sa dami ng numerong iko-connect ninyo, dahil bumababa ang presyo kada numero habang dumarami ang mga ito: US$ 9 bawat isa hanggang tatlo, US$ 7 mula apat hanggang sampu, at bumababa hanggang US$ 2 bawat isa kapag isang daan o higit pa. Ang limang numero ay US$ 35 kada buwan. Libre ang unang 7 araw ninyo, ang pag-alis ng numero ay magtatapos sa singil nito sa dulo ng cycle, at hiwalay ang messaging costs ng Meta na palaging direktang sinisingil ng Meta sa sarili ninyong account.
Naka-disconnected ang numero ko. Ano ang gagawin ko?
Buksan muna ang app sa inyong phone (ang pinakakaraniwang dahilan ay ang 14-day rule). Pagkatapos, patakbuhin muli ang connect flow gamit ang parehong numero: makikilala ito ng Meta, magpapakita ng naka-check na option para i-restore ang dating products, at kusa nitong tatapusin ang reconnection sa loob ng ilang minuto.
Paano ko idi-disconnect ang numero ko?
Sa page ng numero sa dashboard, sa ilalim ng Remove this number. Bawiin namin ang sarili naming access sa Meta, agad na hihinto ang monitoring, at matatapos ang singil sa numerong iyon sa kasalukuyang cycle. Hindi kailanman naaapektuhan ng pag-disconnect ang app: mananatili ang mga chat at history sa phone ninyo, at maaari kayong mag-reconnect sa hinaharap sa pamamagitan ng connect flow.
Hindi nagsi-send ang template ko. Bakit?
Ang pinakakaraniwang dahilan: wala pang payment method ang inyong Meta account. Sisingilin ng Meta ang template sends, lalo na ang marketing, sa sarili ninyong account; magdagdag ng card sa WhatsApp Manager, sa ilalim ng billing, at subukan muli. Tingnan din kung approved ang template (hilingin sa inyong AI ang status nito).
Lalabas ba sa system o AI ko ang mga dati kong conversation?
Kung gusto ninyo lang. Sa connect flow, tatanungin kayo ng Meta kung isi-sync ang chat history sa API side, at maaari ninyong tanggihan. Alinman ang piliin ninyo, hindi kailanman binabasa o sini-store ng EasyCoexistence ang content: nananatili ang history sa phone ninyo, at makakarating lang ang mga bagong message sa sarili ninyong system kung magse-set up kayo ng routing.
Gumagana ba ito sa landline number?
Oo. Kung active ang landline number sa WhatsApp Business app, normal itong mako-connect (may mga customer kaming naka-connect gamit ang landline).
Paano ko babawiin ang access?
Para alisin ang access ng isang AI agent, i-delete ang connector sa sariling settings ng agent. Para alisin ang aming access, i-disconnect ang numero (tingnan ang tanong sa itaas). Naka-encrypt ang mga access token at hindi kailanman inilalantad sa third parties.
Mga Gabay
Mas mahahabang paliwanag na pinagbabalikan ng lahat ng iba pa.
- 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.
Mga Integration
Pag-abot sa isang naka-connect na numero mula sa tool na ginagamit na ninyo.
- 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.
Mga Paghahambing
Ang mga desisyong tinitimbang ng mga tao bago pumili.
- 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.
Pagsisimula
Pag-connect ng numero at kung ano ang susunod na mangyayari.
- 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.
Ang Meta platform
Ang mga account, identifier at verification step na nasa ilalim ng bawat numero.
- 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.
Pagpapadala ng mga mensahe
Ano ang maaaring ipadala, kailan, at ano ang unang sinusuri ng 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.
Mga Webhook
Kung paano nakakarating ang mga event sa inyong systems at kung ano ang laman ng mga ito.
- 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.
Ang MCP connector
Pag-abot sa isang numero mula sa AI assistant.
- 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.
Mga Error code
Bawat error na aktuwal na nararanasan ng aming users, mula sa published reference ng Meta.
100invalid parameter190access token expired368account restricted by policy80007rate limit on the WhatsApp Business Account130429throughput limit reached130497recipient country not allowed131000something went wrong131008required parameter missing131009invalid parameter value131016service unavailable131021sender and recipient are the same131026message undeliverable131031account restricted or data mismatch131042business account payment issue131045phone number not registered131047re-engagement message131048spam rate limit hit131049message blocked for ecosystem health131050the user has opted out131051unsupported message type131052media download failed131053media upload failed131056too many messages to one recipient132000parameter count mismatch132001template does not exist132007template policy violation132012template parameter format mismatch132015template paused for quality132016template is permanently disabled133005incorrect two-step verification PIN133006phone number not verified133008too many PIN guesses133010phone number not registered2593107synchronization limit exceeded2593108sync outside the 24 hour windowcodesWhatsApp Cloud API error codes
Suporta
May tanong ba kayong hindi nasasagot dito? Sumulat sa matheus@tonelotto.com.