Dokumentacija

Šta je EasyCoexistence?

EasyCoexistence postavlja poslovni broj koji već koristite na WhatsApp Business Platformu (Cloud API) putem Metine zvanične funkcije Coexistence, a zatim neprekidno prati vezu kako ona nikada ne bi neprimetno prestala da radi.

• Aplikacija na vašem telefonu nastavlja da radi potpuno isto kao i ranije. Coexistence uz nju dodaje API i ništa ne zamenjuje.
• Nema migracije ni izgubljenih razgovora: istorija ostaje na vašem telefonu.
• Povežite koliko god želite brojeva na jednom nalogu.
• Vaši razgovori nikada ne prolaze kroz naše servere. Dolazne poruke Meta može direktno da prosledi vašem sistemu.

Povezivanje broja

1. Kreirajte nalog i otvorite kontrolnu tablu.
2. Kliknite na „Povežite broj“. Otvara se Metin prozor; prijavite se Facebook nalogom koji upravlja vašim poslovanjem.
3. Unesite poslovni broj i skenirajte QR kod pomoću aplikacije WhatsApp Business na telefonu.
4. Gotovo, obično za manje od 2 minuta. Broj se pojavljuje na vašoj kontrolnoj tabli sa trenutnim stanjem veze.

Da li vaš broj ispunjava uslove? Pročitajte ovo prvo

Meta primenjuje nekoliko pravila pre nego što dozvoli Coexistence. Većina neuspešnih povezivanja nastaje zbog jednog od sledećih razloga:

• Broj mora da bude u aplikaciji WhatsApp Business, verzije 2.24.17 ili novije. Lični WhatsApp nalozi ne mogu da se povežu.
• Broj mora da ima stvarnu i skorašnju dvosmernu aktivnost u razgovorima. Potpuno novi ili neaktivni brojevi se odbijaju.
• Broj ne može da bude povezan sa drugom API platformom ili provajderom (alatima za masovno slanje, CRM sistemima, alatima za automatizaciju). Prvo ga tamo odvojite, pa pokušajte ponovo.
• Verifikacija u dva koraka ili uparivanje uređaja koje čeka u aplikaciji takođe mogu da blokiraju početno podešavanje.

Ako Meta kaže da je broj „registrovan na postojećem WhatsApp nalogu“, NEMOJTE brisati WhatsApp nalog sa telefona; broj mora da ostane aktivan u aplikaciji. Umesto toga, oslobodite ga sa druge platforme.

Šta se menja u aplikaciji (kompromisi)

Uključivanje funkcije Coexistence onemogućava nekoliko funkcija aplikacije, i to samo u pojedinačnim (1:1) razgovorima. Upoznajte se sa njima pre povezivanja:

• Poruke koje nestaju isključuju se u 1:1 razgovorima.
• Poruke za jednokratni pregled onemogućavaju se u 1:1 razgovorima.
• Deljenje lokacije uživo onemogućava se u 1:1 razgovorima.
• Liste za emitovanje: ne možete da kreirate nove, a postojeće postaju samo za čitanje.
• Tokom početnog podešavanja svi povezani uređaji se odvajaju i potrebno je ponovo ih povezati. WhatsApp za Windows i WearOS više nisu podržani.
• Grupe, pozivi, katalog i status nastavljaju da rade u aplikaciji, ali se ne pojavljuju na API strani.
• Broj dobija objedinjeno API ograničenje protoka od 20 poruka u sekundi. Svakodnevno dopisivanje nije pogođeno.

Koristite ga iz svog AI-ja (jedan konektor po nalogu)

Ceo vaš nalog dobija jedan URL konektora. On radi za svaki broj koji povežete, sadašnji i budući: vaš AI vidi sve vaše brojeve i bira odgovarajući za svaki zadatak.

• Claude (web ili desktop): Settings → Connectors → Add custom connector, zatim nalepite URL.
• ChatGPT: Settings → Connectors → Advanced, uključite Developer mode, zatim dodajte URL.
• Claude Code (terminal): claude mcp add --transport http easycoexistence https://easycoexistence.com/api/mcp
• Kada se to zatraži, prijavite se svojom EasyCoexistence imejl adresom i lozinkom i odobrite pristup.

Zatim samo pitajte: „pošalji poruku sa mog broja“, „kreiraj promotivni šablon“, „da li je moj broj u dobrom stanju?“, „prosledi dolazne poruke mom sistemu“.

Šta vaš AI može da radi (alati)

• list_numbers: svi vaši brojevi sa statusom, kvalitetom i nivoom.
• get_number_health: trenutni pregled iz Mete i nedavna vremenska linija događaja.
• send_message: odgovor slobodnog oblika u okviru 24-časovnog perioda za odgovor.
• create_template, get_template_status, list_templates: kreiranje i praćenje šablona poruka.
• send_template: započinjanje razgovora odobrenim šablonom.
• get_api_credentials: ID-jevi, endpointi i token za povezivanje vašeg sistema.
• set_webhook_destination: prosleđivanje dolaznih poruka direktno iz Mete na vaš webhook.
• get_connect_link: način za početno podešavanje dodatnog broja.
• get_docs: ova dokumentacija, kako bi vaš AI mogao da odgovara na pitanja o proizvodu.

Pravila slanja (postavlja Meta, ne mi)

• Odgovaranje je slobodnog oblika: svakome ko vam je poslao poruku u poslednja 24 časa možete direktno da odgovorite.
• Za započinjanje razgovora potreban je prethodno odobren šablon.
• U funkciji Coexistence šabloni mogu da se šalju samo putem API-ja; aplikacija na telefonu ne može da ih šalje.
• Meta naplaćuje marketinške poruke putem načina plaćanja vašeg WhatsApp Business naloga. Mi nikada ne dodajemo maržu na slanje poruka.
• Meta ograničava API protok za brojeve sa funkcijom Coexistence; svakodnevno slanje poruka sa telefona nije pogođeno.

Povežite sopstveni sistem

Stranica svakog broja na kontrolnoj tabli prikazuje njegovu osnovnu URL adresu API-ja, ID naloga i telefona i pristupni token: sve što je potrebno alatima n8n, CRM sistemu ili prilagođenom kodu za slanje putem zvaničnog Cloud API-ja. Za prijem, zatražite od svog AI-ja da prosledi dolazne poruke na vaš webhook (set_webhook_destination): Meta ih zatim isporučuje direktno vašem endpointu i nikada ne dodiruje naše servere.

Praćenje i pravilo od 14 dana

Neprekidno pratimo svaki povezani broj (stanje veze, ocenu kvaliteta i nivo slanja poruka) putem Metinih webhookova i periodičnih provera. Ako se poslovna aplikacija na telefonu ne otvori oko 14 dana, Meta može neprimetno da prekine Coexistence vezu. Čim se bilo šta pokvari, vaša kontrolna tabla to prikazuje zajedno sa razlogom. Pravilo za svaki dan: koristite aplikaciju normalno.

Šta EasyCoexistence nije

• Nije prijemno sanduče ni chatbot. Razgovori se i dalje odvijaju u vašoj aplikaciji, vašem AI-ju ili sopstvenom sistemu; ne dodajemo još jednu kontrolnu tablu u kojoj morate da živite.
• Nije alat za masovno slanje poruka. Metina pravila i dalje važe: odgovori u roku od 24 časa, a za započinjanje razgovora šabloni.
• Nije Metin proizvod. Mi smo nezavisni Tech Provider koji koristi Coexistence, zvaničnu funkciju platforme.
• Nije posrednik za vaše poruke. Nikada ne čitamo niti čuvamo sadržaj vaših razgovora.

A ako EasyCoexistence sutra nestane? Vašem broju se ništa ne dešava: aplikacija nastavlja da radi, istorija ostaje na telefonu, a API veza može da se prekine u bilo kom trenutku. Most, a ne kavez.

Česta pitanja

Vodiči

Duže objašnjenje na koje upućuje sve ostalo.

• 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.

Integracije

Dostizanje povezanog broja iz alata koji već koristite.

• 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.

Poređenja

Odluke koje ljudi razmatraju pre izbora.

• 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.

Početak rada

Povezivanje broja i ono što se dešava zatim.

• 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.

Metina platforma

Nalozi, identifikatori i koraci verifikacije koji stoje iza svakog broja.

• 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.

Slanje poruka

Šta može da se pošalje, kada i šta Meta prvo proverava.

• 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.

Webhookovi

Kako događaji stižu do vaših sistema i šta sadrže.

• 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 konektor

Dostizanje broja iz AI asistenta.

• 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.

Kodovi grešaka

Svaka greška sa kojom se naši korisnici zaista susreću, prema Metinoj objavljenoj referenci.

• 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

Podrška

Imate pitanje na koje ovde nema odgovora? Pišite na matheus@tonelotto.com.