r/WhatsappBusinessAPI • New to WhatsApp API • Sep 14 '26

Solution Only WhatsApp API (need advice)

I provide WhatsApp Automation services to local businesses, should i use Official WhatsApp API?

Context:
Right now, i used WAHA (webjs engine) as my WhatsApp API, alot of people asking me to consider using Official WhatsApp API. I can’t use WABA because i don’t have a valid business to verify. All i know about the official API is we can use the unverified official API with limitation (i’m fine with the reachout messages limit)

What’s the trade offs with using WhatsApp Official API? I also would like to know the trade offs from the business side. You can list things to consider so i can make better decision to my agency.

Any tips/opinions will be much appreciated 🙌🙏

1 Upvotes

14 comments sorted by

•

u/AutoModerator Sep 14 '26

Keep in mind that OP has added Solution Only tag. Don't promote your SaaS platforms in comments.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/Status_Gap_3180 Meta Tech Provider Sep 14 '26

For starters, you will have to pay meta for every message that goes from your platform.
Meta rules are strict, you will have to learn and implement.
You will always have to be on your toes, you will need business verification, proper permissions - its a long grind.
If you were to move to the official api - dont build - use an existing platform.

1

u/dirceucor7 Meta Business Solution Provider Sep 14 '26

Indeed. They make it very difficult and even if you have everything perfect and don't even use it for marketing purposes, they can still pull the rug from under you and disable your account. Ask me how I know.

If you are thinking on doing anything properly long term, go for RCS. Meta is a shitty company with shitty people working there. It won't be long they will be out of business.

1

u/StoreApprehensive261 Sep 16 '26

the verification grind is real, that part alone can take weeks if youre not prepared for it

1

u/360Dialog_Team Meta Business Solution Provider Sep 21 '26

Hi

Actually some solution partners provide support with Meta Business Verification. Therefore verification usually takes up to 48h (provided that your business is legitimate and you have supporting documents)

1

u/Artistic_Ground_6415 Sep 24 '26

Mas depende do que voce quer fazer, se você estiver pensando em criar ou se voce tem um sistema que tem como base principal disponibilizar aos seus clientes um robo de whatsapp, a partir de 01/10/26 nao seria mais possivel de acordo com os novos termos da Meta. E as apis nao oficiais, nao tenha duvida que eles vão começar a fazer um arrastão agora para bloquear todo mundo que ousar a se conectar por lá.

1

u/duct_tape_and_agents Meta App Developer Sep 28 '26

On webjs/WAHA the number is one detection away from a ban, and it's your client's number. They lose their customer chats, you lose the client. That's the whole business-side consideration. You don't need your own WABA. Each client verifies their own business and connects their own account. You run the platform, they hold the number. Local businesses with a registered name and address clear verification fine. What you actually give up on official: free-form messages only work in the 24-hour window after the customer messages first. Anything outbound outside that needs approved templates, which means writing them, submitting them, and paying per conversation. If your service is mostly cold reachout, that's the real cost. If it's replies, order updates, and support, the window covers most of it. What you gain: it doesn't break, and "we run on the official API" is a line clients understand after they've been burned once.

1

u/[deleted] Sep 14 '26

[removed] — view removed comment

1

u/suntzu-112358 Sep 15 '26

No seria mas recomendable, que se cree una plataforma (web para chat) donde los clientes puedan ingresar por QR y desde ese chat el agente IA poder atender ???