Meta Tech Provider

The risk is not the software.It is the number.

Unofficial WhatsApp APIs work by signing in as a linked device and automating the WhatsApp Web session. That is what WhatsApp's terms prohibit, and it is the number that pays for it, not the tool. The official Cloud API does the same work through an interface Meta supports.

Start Free Trial7 days free. Nothing is charged until the trial ends.
Where the two routes diverge
UnofficialYour server holds a paired WhatsApp Web session
OfficialMeta’s Cloud API, on a number the app still uses
No guardamos mensajesBusiness App + Cloud APIMCP para Claude y ChatGPTEn vivo en 2 minutos

What an unofficial WhatsApp API actually is

Whatever the marketing says, they all do the same thing underneath. Knowing the mechanism is what makes the rest of this page obvious.

  1. 1
    It opens the WhatsApp Web protocolThe same one the browser client speaks. Nothing about it is a private API or a special integration.
  2. 2
    It pairs itself as a linked deviceYou scan a code, exactly as you would to use WhatsApp in a browser. From then on the library holds that session.
  3. 3
    It drives the session programmaticallyMessages are read off the socket and pushed back through it. This is why it installs in minutes and needs no account, review or approval.
  4. 4
    The session lives on your serverThose credentials are full account access, and they are a known target. There is nothing equivalent to revoke.

What the terms say, and why anti-ban claims cannot work

WhatsApp's terms prohibit automated and bulk use of the consumer client. A linked device is the consumer client, so the prohibition covers the mechanism itself rather than any particular library.

That is the part worth sitting with. A tool advertising anti-ban protection is claiming to control something outside of it, because what is prohibited is not the code sending the message. Rewriting the library, rotating the session or slowing the sends changes the implementation, not the category.

It is also why months of uptime is not evidence of safety. It is evidence that nothing has happened yet, which is a different statement and a much weaker one.

What it costs when it goes wrong

The failure is not that automation stops. It is that the number stops, and for most businesses the number is closer to a phone line than to a piece of software.

Customers cannot reach you

Every conversation on that number becomes unreachable, and the people in them are told nothing. They simply stop getting replies.

The number is printed on things

Vans, storefronts, cards, invoices, a website, years of past messages. None of that can be recalled.

The history goes with it

Threads, and the contact list that only existed inside them.

For an agency, it is a client's number

One that was never told this was the mechanism underneath what they bought.

What the official route actually costs you

This is the honest part, and it is short. The official API is more restricted, and the restrictions are real rather than something a provider can lift.

24 hoursFree text has a window

Outside 24 hours from the customer's last message, only a template Meta has approved will deliver.

ApprovalTemplates are reviewed

Anything that opens a conversation is submitted to Meta first. Usually minutes, sometimes a day.

No groupsGroup chats are excluded

Not available through the API on a Coexistence number, on any provider.

In exchange the number cannot be banned for the mechanism, because the mechanism is the one Meta publishes.

Moving off one without losing the number

The objection to the official API used to be real: it meant migrating the number, which killed the WhatsApp Business app on it. Coexistence removed that, so the move is smaller than most people expect.

  1. 1
    Stop the unofficial sessionLog the linked device out from the phone. The number itself is untouched by this.
  2. 2
    Connect through Meta's own flowEmbedded Signup, then a code scanned in the WhatsApp Business app. Two to three minutes, and the app keeps working.
  3. 3
    Point the webhook at what you already builtYour existing handler mostly survives. What changes is the payload shape and that delivery now comes from Meta directly.
  4. 4
    Rebuild anything that used groupsThis is the one genuine rewrite, and it is worth knowing before you start rather than after.
20 msg/s

Throughput de la Cloud API oficial en un número en Coexistencia, fijado y garantizado por Meta.

24 hours

Cuánto tiempo mantiene abierto el texto libre la respuesta de un cliente en la API oficial.

0 sessions

Credenciales que la vía oficial guarda en tu servidor, porque no hay sesión que emparejar.

Preguntas frecuentes

¿Mi número ya está en riesgo si uso una de estas?

La exposición existe mientras la sesión esté corriendo. Nada se dispara en una fecha fija, y por eso un buen tiempo en línea no tranquiliza. Pasar a la API oficial en el mismo número es posible sin perder la app.

¿Puedo pasar a la API oficial sin cambiar de número?

Sí. La Coexistencia conecta el número que ya usas, y la app de WhatsApp Business sigue funcionando en el celular todo el tiempo. Nada migra.

¿Qué no puede hacer la API oficial?

Los grupos quedan excluidos en números en Coexistencia. El texto libre solo funciona dentro de las 24 horas del último mensaje del cliente, y fuera de esa ventana los mensajes deben usar una plantilla aprobada por Meta.

¿La vía oficial cuesta más?

Meta cobra sus propias tarifas de mensajería de todas formas, facturadas directo a ti. La diferencia es una tarifa fija mensual por número en vez del riesgo de perder el número.

¿Listo para empezar?

Configura WhatsApp Coexistence en minutos, no en meses. La app sigue funcionando en el teléfono.

Start Free Trial7 days free. Nothing is charged until the trial ends.

Keep reading

Riesgos de API no oficial