r/WhatsappBusinessAPI

I have created an app for a client . The client needs to send messages for important updates, login codes etc to their app users using whatsapp automatically. For this case suggest an WhatsApp api provider that doesn’t have monthly fee. Just per message fee. As my message volume will be max 500 msg per month approximately.

**Suggest some api providers.**

I’m looking for a virtuali number free or to pay to use on Whatsapp B.

I already tryed wabi, zadarma, twilio without having a good experience.

Other suggests?

Hi, I am going to start working on a project which needs to build a unified inbox using whatsApp and emails.

I am currently looking into possible solutions which would help me build WhatsApp message ingestion service. So basically other business who have multiple "operations coordinators" will use our platform to use unified inbox and manage their conversation from single place.

There's an option that we go directly with Meta and use their API as a Tech Provider but this needs more time and work from our end. On the other hand, I am looking into Twilio and of course other alternatives. Now I just need to understand how exactly Twilio can help us such that for each company, we can have multiple whatsApp numbers registered with us so that we can send/receive messages from our platform.

Any guidance? Any devrel or support team from Twilio can help us with this? We are a new early-stage startup and we are looking for serious help. Thank you

I've been thinking about how businesses are trying to connect with customers today.

For years, the standard journey has been something like:

Ad/Search → Website → Form → Email/Call → Follow-up

Then many businesses moved towards:

Download our app → Register → Login → Learn the interface → Complete the task

But for many everyday service interactions, customers are already messaging businesses.

This raises an interesting question:

For which business interactions does a dedicated mobile app still provide real value, and when is a conversational channel like WhatsApp more practical?

I can see arguments for both sides.

A dedicated app can provide deeper functionality, structured transactions, loyalty features and greater control over the customer experience.

WhatsApp can reduce friction for enquiries, qualification, appointment scheduling, order-related conversations, reminders, follow-ups and human assistance because the customer is communicating through a channel they already use.

But there are trade-offs too: platform dependency, privacy considerations, notification limitations, automation quality and the danger of businesses turning a personal messaging channel into another source of unwanted marketing.

I'm curious how people here see this evolving.

As a consumer, would you rather download a company's app for occasional transactions, or message the business and complete most of the journey through conversation?

And from a business perspective: where does an app remain essential, and where is messaging actually the better interface?

Dude i was imagining to become a tech provider
for medium sized businesses and provide some cool features like sheets and open ai and memory storage of customers etc
and then i was just scrolling through this sub reddit
read through somewhich said meta is completely changing the plan
and gonna charge per messages etc
in that case my whole pricing model i had created goes down the drain
which was about
50$ per month with 24/7 support and updates and changes etc
as a basic plan and higher plans for higher leads and etc

i was plannito target
travel business,resorts in india
dentists,other service providers in usa,australia,and african countries 😭😭

should i actually do it or just moveon???

so if am using manychat or other mate approved app for whatsapp management and auto replies to customers with in the first 24h interaction window, the charge will not be free anymore ?

I have done all these steps

1. callback url is verified
2. the webhook url return forbidden(hence working)
3. subscribed to messages
4. node terminal shows the test message payload
5. tried cloudflare and ngrok both just showed test messages response and had a 200 ok
6. even tried render same scenario
7. have my number in the recipients cell number
8. also have the app mode at live

so after all these still i am just unable to see my payload in the terminal
when i am sending a msg from my personal no to the test number

how do i solve this when i have checked all the boxes???
can someone pls guide me through this
on a call or smtg

I want to sort out a billing thing before I build around it.

My client takes orders through WhatsApp. My plan is to connect their number to the Cloud API in Coexistence mode, but only to listen and record incoming messages through webhooks. They keep replying to customers by hand from the WhatsApp Business app. I never send anything through the API.

The thing I can't figure out is the Oct 1 2026 change where service messages stop being free and get billed per message.

So if the number is connected via Coexistence and the client replies from the app, does Meta count that reply as a billable service message? The WABA is on the Platform and app messages get echoed to the API as smb_message_echoes, so I don't know if those echoes get metered or if billing only kicks in when there's an actual API send call.

Basically what I need to know is whether the charge is triggered by the message going through the API, or just by the number being API connected no matter where the reply comes from.

If anyone is running Coexistence right now and can check their billing after replying from the app, that would settle it for me. I already know receiving is free. It's only the app reply I'm unsure about.

Hola a todos,

Estoy teniendo un problema bastante raro con WhatsApp Business App Coexistence y YCloud, y quería saber si alguien pasó por algo parecido.

Conecté el número actual de WhatsApp Business a YCloud usando su flujo de Coexistence.

El proceso de vinculación termina correctamente y, desde Meta/WhatsApp, aparece que el número está conectado a una plataforma empresarial.

Sin embargo, dentro de YCloud:

• No aparece ninguna cuenta en “WhatsApp Accounts”.
• No puedo crear plantillas de mensajes.
• La WABA parece no estar completamente vinculada.
• Pero, extrañamente, sí aparecen mis contactos.
• También aparecen las conversaciones de WhatsApp en la bandeja de entrada de YCloud.
• Mi webhook de n8n recibe eventos.

Entonces parece que la cuenta está conectada parcialmente, pero la WABA no quedó correctamente asociada a YCloud.

Al principio, el soporte de YCloud me dijo que el problema estaba relacionado con que la moneda de la WABA no era AUD y que posiblemente la cuenta había estado vinculada anteriormente con otro proveedor.

Este número nunca estuvo conectado a otro proveedor externo de WhatsApp API.

Cambié la moneda a AUD como me indicaron, desconecté la conexión de “Plataforma empresarial” desde WhatsApp Business App y volví a completar todo el proceso de Coexistence.

El resultado sigue siendo exactamente el mismo.

Meta/WhatsApp muestra que la conexión con la plataforma empresarial está activa, los contactos y chats aparecen en YCloud, pero la cuenta de WhatsApp no aparece dentro de YCloud y no puedo administrar ni crear plantillas.

¿Alguien tuvo antes este problema de conexión parcial con Coexistence?

Cualquier ayuda o explicación técnica me serviría mucho.

For almost two years, Meta let us reply to our own customers for free inside the service window. Businesses, agencies, and independent devs built entire products, workflows, and livelihoods around that promise. Small support teams restructured around it. The whole ecosystem exists because Meta said, "this is free, build here."

Now, starting October 1, they're just taking it back. Per-message charges are returning for service replies, the exact thing thousands of us use every single day to actually talk to our customers with multiple rich messages; now they're essentially rug-pulling us to launch a half-baked agent platform.
We are the ecosystem they built this platform's reputation on. We deserve better; we need to band together and make our voices heard, rather than just bitch and moan on reddit. I'm down to create a Discord or Telegram group where we could brainstorm and come together to present a unified opposition to this, any takers?

If you have not heard, meta is basically killing agents on whatsapp.

Starting from October they will charge ~1 cent per message, regardless if the user initiated contact or not, or if it's mid conversation or not.

This makes many businesses that run agents unviable, or increase the cost to end consumers.

I'm trying to come up with alternatives.

Alice&Bot is a free and open source WhatsApp clone targeted at ending the monopolies of whatsapp and telegram.

Supergreen is a service that allows you to turn normal whatsapp accounts into an API.

If you care about IM freedom, check out these projects.

Meta wording is extremely confusing. So I wanted to have a discussion to actually understand the pricing updates.

My clients are integrated with an omni-channel inbox platform to centralize customer communications in one inbox.

They DO NOT use AI at all. 100% human responses.

Most of them DO NOT send marketing/authentication/utility messages or any message outside of the 24h customer service window. Because of that, they pay near 0 for API costs.

And here's what the Pricing Updates email I got a few days ago says:

> Effective October 1, 2026, Meta will resume charging for service messages on a per-message basis ... Per-message rates for service messages will be the same as those for utility and authentication messages, by market.

In my market Utility templates outside of the 24h customer service window are $0.0113 and one of my clients did 15k outbound messages in May within the 24 hour customer service window. That means they would get charged 169 USD for using the API without ever sending messages outside of the 24h customer service window?

Am I getting it right?

Title: WhatsApp Web calls work Web-to-Web and Mobile-to-Mobile, but fail between Web and Mobile

I’m trying to diagnose a WhatsApp calling issue and wanted to see if anyone else has seen the same pattern.

## Environment

- macOS

- WhatsApp Web running in Chrome / Electron-based WebView

- Proxy/VPN/TUN tested with multiple nodes

- UDP/STUN appears to work

- `RTCPeerConnection` exists in the browser

- Public IP changes correctly when proxy is enabled

## What works

I tested several combinations:

| Call direction | Result |

|---|---|

| WhatsApp Web ↔ WhatsApp Web | Works |

| Mobile WhatsApp ↔ Mobile WhatsApp | Works |

| WhatsApp Web ↔ Mobile WhatsApp | Fails |

This happens even when Web-to-Web calls are using different proxy nodes, and Mobile-to-Mobile calls also work across different nodes.

## What fails

When calling between WhatsApp Web and a mobile WhatsApp client:

- The call rings.

- The other side can answer.

- After answering, the call stays stuck on “Connecting”.

- Eventually WhatsApp shows a network-related warning, such as asking to check or switch the network.

- Media never connects.

## Things I already checked

- WebRTC exists:

```js

typeof RTCPeerConnection

// "function"

I’ve been tempted to banned twice on less than three days, what am i doing wrong?

I run a volunteer company for english tutors. Highschool Tutors volunteer online to teach kid english.

I used to use telegram but once it got banned recently by India i went to WhatsApp Business. And i have made sure all my staff has us in contact, that they messaged us first, i have an entire community (group) of 65 members and its consistent. We chat in there, we send schedules and announcements and also the tutors can ask for substitutions for classes.

I filed a dispute the first time. My account was let go after 24 hours.

Then i didnt really message much on it and i just messaged one of my tutors and boom blocked again for 24 hours. And i just dont understand what im doing incorrectly at this point. Im sick and tired of this crappy app. I have also messaged the contact centre for whatsapp but what is that gunna change

Meta recently announced that they would be charging for service message from October 1sr onwards.

With this they are doing everything to extract money from the business directly.

The margin for tech provider and tech partner are minimal.

Only a few BSP are making good money of WhatsApp platform and rest all tech partner and provider are just providing free service to Meta.

Maybe we should have a union where we go on a strike on any one specific day where none of us send any messages from our platforms.

This move by meta will discourage mid to small scale business from onboarding the whatsapp business api. What's your thought on this.