WhatsApp Business API / Meta Cloud API.

Hello.

Yes, I work specifically with the official Meta WhatsApp Business Platform / Cloud API, without QR codes, WhatsApp Web, Baileys, and gray gateways.

In your case, the key point is coexistence. Currently, Meta has a scenario for connecting an existing WhatsApp Business App number to the Cloud API, but availability depends on the account, country, number type, WABA, Business Manager, and the current status of the number. Therefore, as the first step, I would not blindly transfer the number but would check the possibility of connection.

Here’s how I will proceed:

1. I will check the Business Manager / Meta Business Suite.
… 2. I will check the company status and the possibility of creating or connecting WABA.
3. I will check if the current WhatsApp Business number can be connected in coexistence mode.
4. I will check the limitations regarding the number, verification, display name, and access.
5. After the check, I will provide a precise conclusion: whether it can be connected without losing the WhatsApp Business App or if another scenario is needed.

For the check, I need:
— access to Meta Business Manager;
— admin access or an invitation as a partner;
— WhatsApp Business number;
— access to the phone with this number;
— company website;
— legal company details, if verification is required;
— understanding of where the customer base will come from and what types of messages are planned.

If coexistence is available, I will proceed to connect:
— WABA / Cloud API;
— webhook for incoming messages;
— sending messages from the web service;
— statuses sent / delivered / read / failed;
— message templates for communication after 24 hours;
— basic CRM version: chat list, responses, templates, mailing to your own base.

Cost:
— checking the possibility of coexistence: from ___
— connecting Cloud API + webhook + sending/statuses: from ___
— first version of the dashboard with chats, templates, and mailing: from ___

Timeline:
— check: 1–2 working days;
— API connection: 2–4 working days;
— simple first version of the web service: 5–10 working days, depending on requirements.

I can explain a similar case technically: the connection goes through the official Meta Business Manager, WhatsApp Business Account, Cloud API, webhook endpoint, permanent access token/system user, setting up message templates, and processing statuses through webhooks.

I suggest starting with the number check to avoid risking the current operation of the WhatsApp Business App.

Show original

Translate

Hello! I have done official integrations through the Meta WhatsApp Cloud API / WABA — the official way, without QR, Baileys, and Green API, as you requested.

Regarding coexistence: yes, I have worked on it. First, I will check if your number is eligible — coexistence is not available for all numbers and depends on how the number is currently registered in the WhatsApp Business App. This is the first and quickest step: we confirm eligibility and only then connect, so as not to disrupt anything in the current operation.

Steps:
1. Check the possibility of coexistence for your number + list of accesses and documents for Meta (Business Manager, verification).
2. Connect WABA / Cloud API: incoming through webhook, outgoing from the web service, statuses (sent, delivered, read, error).
3. Approved templates for messages outside the 24-hour window and a simple first version: chats, responses to clients, templates, mailing to the database.

… Please clarify: is the number currently linked to a personal Facebook or to Business Manager? This affects how the coexistence onboarding will proceed.

I am taking it at a starting price — I am gathering initial reviews on Freelancehunt, so I am offering a good deal. I am ready to show live how everything works. Timeline: checking 1-2 days, full connection about 5-6 days.

Petro Pankov, BotCraft Group

Show original

Translate

I recently helped a client understand the limitations regarding the number before integration, so I understand well how important it is to first check the possibility of coexistence before connecting anything. Otherwise, you might waste time on setup that ultimately turns out to be unavailable for a specific number or Business Manager configuration.

I would start by checking your number, the status of your Meta business account, and the availability of the coexistence mode. After that, you can calmly connect the API, set up message reception and sending, delivery statuses, templates, and the interface for working with chats.

Could you let me know if the number is already linked to Business Manager and a verified Meta company? Are you planning to use a ready-made web service for chat management or do you need your own interface? And on which platform is your service currently running, where you need to connect the WhatsApp API?

Show original

Translate

Hello! Yes, I raised the official Cloud API through Embedded Signup — incoming via webhook, delivery statuses, and read, approved templates for messages after 24 hours. I also did coexistence: the number remains in the WhatsApp Business application and works simultaneously through the API, without transfer and loss of history. However, it is not available for every number, so first I will check specifically for yours. Can you tell me if the number is currently on Android or iPhone? This affects whether it can handle coexistence. I will do the check in a couple of days, then proceed with the connection and sending/receiving.

Show original

Translate

Hello, Bakhytzhan! I am ready to complete your project: "WhatsApp Business API / Meta Cloud API."... Write to me, and we will discuss the details!

Show original

Translate