WhatsApp Business API / Meta Cloud API.

Budget: 25000 USD Deadline: 18 days

Yes, we have worked with the official Meta WhatsApp Cloud API and WABA - webhooks, statuses sent - delivered - read - error, templates, roles, and simple operator panels. We can start the coexistence mode with a separate number verification, as availability depends on the status of the number in the WhatsApp Business App, Business Manager, WABA, and passing the Embedded Signup. We do not use gray QR codes and WhatsApp Web =)

Regarding costs - checking the possibility of coexistence and connection map is 12,000 UAH, 2 days. Connecting the Cloud API plus the first version with chats, responses, templates, and mailing to your database - the estimate is 72,000 UAH, up to 18 working days. If after verification it turns out that the number cannot be connected in coexistence without restrictions, we will not drag you into unnecessary development.

I will work step by step - checking the Meta business account and number, connecting WABA, setting up webhooks for incoming messages and statuses, sending from the web service, templates after 24 hours, a minimal chat and mailing cabinet. I need administrator access to Meta Business, the number, business confirmation if required, domain, and access to the web service or server from you.

I would like to clarify two points:
> Is the number already linked to Meta Business or only to the WhatsApp Business app on the phone?
> Does the web service already exist or does the chat panel need to be created from scratch?

Similar in logic:
> https://business.ingello.com/forma-crm - cabinet, roles, and workflows
> https://business.ingello.com/vorfahr - automation with API and business logic, close to the integration task
> https://systems-fl.ingello.com - main profile of Ingello Systems for the exchange. Expand

Budget: 3500 USD Deadline: 2 days

Hello. I work with the Meta Cloud API and WhatsApp Business webhooks. Regarding your situation: coexistence can indeed be set up, the number will remain in the WhatsApp Business application on the phone and will be connected to the API via Meta simultaneously, without disrupting the current operation. First, I will check if the number is suitable for coexistence, advise on what access and business verification are needed from Meta, then I will connect it and link it to your web service for receiving and sending messages. The price is 3500 rubles, and the timeframe is 2 working days.

Budget: 1000 USD Deadline: 7 days

Bakhytzhan, you have the correct request: it is important to first check if coexistence is supported for your number specifically, so as not to break the current WhatsApp Business App. I have already worked with web services and API integrations, so I will help step by step: checking the possibility, preparing data for Meta, connecting Cloud API/WABA, incoming/outgoing, statuses, templates, and the first version of chats. We can start with a quick check and immediately determine the work plan.

Budget: 1500 USD Deadline: 7 days

Hello, Bakhytzhan!

I looked at the proposals from other specialists and want to offer my solution so that you have the opportunity to communicate not only with GPT chats.

I will refrain from a specific proposal for now, as it is important to start from the ultimate goals of your project. I need more information for more accurate recommendations.

Please clarify:
- Deadlines for connection and setup: is there a time buffer or is urgent implementation needed?
- Do you have a technical specification for integrating the WhatsApp Business API?
- Have you previously worked with Meta WhatsApp Cloud API / WABA in coexistence mode, and what were the results?
- Can you provide examples of successful integrations or explain how you plan to use the API in your project?

The cost and timelines for connection are influenced by:
1. Checking the possibility of coexistence for your number.
2. The volume and complexity of integration with your web service.
3. Availability of all necessary accesses and documents for Meta.
4. Setting up functions: receiving and sending messages, statuses, approved templates, etc.
5. Your vision of the final result and the presence of a technical specification.

It is important to formulate and agree on the final vision of the WhatsApp Business API integration. I prefer to build this vision based on successful cases and your wishes to offer the most effective solution.

I understand that it is important for you to maintain the current work of the WhatsApp Business App and connect the API. I have experience with Meta WhatsApp Cloud API and coexistence solutions. I am ready to help with checking the connection and setting up the necessary functions for your business.

The next step is to discuss your project in detail and understand how well we fit together. Let's fix all the details in correspondence or at a meeting. Expand

Budget: 25 USD Deadline: 1 day

Good day.

I can start with a paid technical audit of WhatsApp Business and Meta Cloud API.

In the first stage, I will check:

— the possibility of coexistence for the current number;
— the status of Business Manager and WABA;
— access and verification;
— the ability to send and receive messages;
— template requirements;
— the actual scope of integration.

The cost of the first stage is $20–30. Based on the results, I will provide a detailed plan, budget, and timeline for full integration.

I can start today. Please let me know if the Meta Business Manager has already been created and if this number is being used in regular WhatsApp Business? Expand

Budget: 300 USD Deadline: 14 days

Good day!
I will answer your main question right away to save time: there is no official "coexistence" (app + Cloud API on one number).
Meta's rules are strict: a number is linked either to a phone (WA Business App) or to WABA (official API). When the API is activated, the app on the phone is irreversibly disabled. Those who promise you parallel operation are using "gray" workarounds via QR code (Baileys/Green API), which you yourself rejected in the terms of reference.
Here’s how we can proceed (exclusively "legally"):
1. Allocate a separate number specifically for WABA.
2. Or completely transfer the current number to the API. The app on the phone will not work, but we will bring all chats into a convenient web interface or connect a ready-made CRM.
Regarding other points:
Experience: Yes. I have integrated Meta Cloud API, set up webhooks and templates.
Documents: A verified Meta Business Manager (data of an individual entrepreneur/legal entity) and a website will be required. I will help with the setup and confirmation.
Implementation: I will write the logic for receiving/sending messages, status processing, and template registration.
Web version: I can create a custom chat interface with broadcasts, but it will be cheaper and more reliable to link the API with an already existing CRM system.
Estimated time and budget (for API integration + basic custom web chat):
Time: 10–14 days.
Budget: 300 USD.
My portfolio: https://aleksandergladchenko.github.io/portfolio/
If you are ready to reconsider the concept of using one number — write to me, we will discuss the details and start working. Expand

Budget: 250 USD Deadline: 4 days

Hello, Bakhytzhan! I only work officially — through WABA + Cloud API, without QR/Baileys/Green API (for business numbers, gray gateways = risk of ban, you are right).

Regarding coexistence, to get straight to the point, so you see the real picture:
Yes, this is the official Meta mode (launched in May 2025): your number remains in the WhatsApp Business App and works simultaneously through Cloud API, without transfer and loss of history. Connection is through Embedded Signup.
But availability depends on the number and region — so the first step is always to check the eligibility of your specific number; I do not connect blindly.

And honestly about your task (so there are no surprises later):
— Chats, responses, incoming/outgoing, statuses, approved templates in coexistence work as expected.
— However, mass mailing to the database in coexistence is limited: this mode has reduced throughput, Meta slows down bulk mailings in favor of regular API numbers. If mailing is critical for you in volume — I will show options during the eligibility check (a separate API number for mailing), so you can choose consciously.
— The blue badge (OBA) in coexistence is currently unavailable — if it is needed, that is a separate path.

Plan:
Stage 1 — check the eligibility of your number (region, history, account status) + list of accesses and documents for Meta. Quick, and you do not pay for connection blindly. Duration: 2 days. Cost: 40 USD.
Stage 2 — after the check: WABA + Cloud API, incoming via webhook, outgoing from the web service, statuses (sent/delivered/read/error), approved templates for the window outside 24 hours, and the first version — chats, responses, templates, mailing to the database. Duration: 5-7 days. Cost will be clarified after Stage 1 (depends on the eligibility result), estimate 200-250 USD.

We work through a Secure Deal. What would be the most convenient way to start the check — will you send access to Meta Business Manager? Expand

Budget: 200 USD Deadline: 6 days

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 Expand

Budget: 250 USD Deadline: 10 days

I will only take on the official WhatsApp Business API / Meta Cloud API scenario without QR, WhatsApp Web, Baileys, Green API, and other gray solutions: first, I will check the possibility of coexistence for the current number, then WABA, webhooks, incoming/outgoing messages, statuses, templates, and basic web logic for chats.

Is it important for you to first check if the current working number can be connected without deleting the WhatsApp Business App, transferring the number, and stopping communication with clients?

Budget, deadlines, and a step-by-step plan will be discussed in private correspondence after reviewing the Meta Business Manager, the current WhatsApp Business number, WABA/account, verification status, access, web service requirements, templates, mailing, and message processing logic.

Budget: 90 USD Deadline: 6 days

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.

Budget: 200 USD Deadline: 5 days

Good day! I have worked with the official Meta WhatsApp Cloud API / WABA - webhooks, statuses (sent/delivered/read/error), approved templates, and coexistence mode. The first step is to check the eligibility of your number for coexistence (depends on Business Manager, type of number, and Meta verification) to avoid disrupting the current operation of the application. After confirmation, I will connect WABA through Embedded Signup, set up incoming/outgoing via webhooks, templates for messages after 24 hours, and a basic web interface for chats and broadcasting to the database.

Budget: 3000 USD Deadline: 12 days

Greetings! Yes, I have real experience working with the official Meta WhatsApp Cloud API (WABA), and I am well acquainted with the Coexistence mode (simultaneous operation of the application and API).

Checking the possibility of Coexistence for your number
Yes, it can be checked and configured. The main criteria for a number to qualify for Coexistence are:

The number must already be registered in the WhatsApp Business App (a regular personal WhatsApp will not work; you will first need to make a free transition to the Business version).

The number must not have been previously hard-migrated to the Cloud API with the account being removed from the application.

The number must be "clean" in terms of bans from Meta.

The check itself: I will do it for free as part of the first stage of work, as this is a basic diagnosis before connection.

My work on the setup: $1000–$1500 for a complete "turnkey" setup (creating WABA, linking to your Facebook Business Manager, going through Embedded Signup, setting up webhooks and synchronization).

Official payments (Meta and Provider): The connection from Meta is free. However, for the API to send/receive messages, we will need a connector/platform (for example, Albato, Make, or a specialized CRM/Inbox system).

Day 1: Checking the number, preparing Meta Business Suite, creating a WABA account.

Day 2: Launching Embedded Signup, generating a QR code, pairing, and starting history synchronization.

Day 3: Testing message sending (echo responses) and finalization. Expand

Budget: 50 USD Deadline: 1 day

I have worked with the Meta Cloud API and understand the situation: many are afraid that connecting the API will automatically break the app on their phone, but this is not necessarily the case. It can be set up through Business Manager without transferring the number, keeping the current WhatsApp Business on the device operational while simultaneously gaining access to the API for sending via webhooks or third-party services. The main question is: what is the ultimate goal of connecting the API, that is, what exactly needs to be done through it, such as newsletters, chatbots, integration with CRM? I am ready to delve into the details and help set everything up without losing current functionality.

Budget: 1300 USD Deadline: 15 days

Good day. I am ready to work, I have experience. Feel free to contact me.

Budget: 350 USD Deadline: 10 days

Hi hope you are doing well

I can help you connect WhatsApp Business through the official Meta WhatsApp Cloud API and first check whether your current number can use coexistence while still working in the WhatsApp Business App.

My first step will be to review your Meta Business Manager WhatsApp Business account phone number status business verification and current WhatsApp setup. Then I will explain clearly what access documents and permissions are needed before making any changes.

If coexistence is available for your number I can assist with the WABA and Cloud API setup webhook configuration incoming messages outgoing messages message status tracking sent delivered read failed and approved templates for messages outside the 24 hour window.

I can also build a simple first version with chats replies customer message history templates and basic mailing to your database using only the official Meta API.

I do not use gray QR WhatsApp Web Baileys Green API or unofficial methods.

I have experience with API integrations webhooks messaging systems templates dashboards and customer chat workflows.

Best regards
Youssef. Expand

Budget: 25000 USD Deadline: 14 days

We already have a nearly ready solution for the official WhatsApp Business API, which can be quickly adapted and launched for your task.
I’m here, we can discuss the details right here ))

Regarding your questions - yes, we have worked with the official Meta WhatsApp Cloud API, WABA, webhooks, templates, message statuses, and simple CRM interfaces for operators.
Coexistence needs to be checked for a specific number and Business Manager settings, as the country, number type, WhatsApp Business App status, company verification, and feature availability in your Meta account are important.

The cost for checking coexistence and preparing a roadmap starts from 8,000 UAH, usually taking 1-2 days.
Connecting WABA, webhooks, sending, incoming messages, statuses, templates, and the first version of chats is estimated at 45,000 UAH and about 10-14 working days.
If it turns out after the check that coexistence for the number is unavailable, we will show an official migration option without gray solutions and without breaking current processes, as far as Meta allows.

Here’s how I would proceed step by step:
- Check Business Manager, WABA, number, permissions, company verification, and eligibility for coexistence.
- Set up Cloud API, webhooks, signature verification, incoming events, and statuses sent, delivered, read, failed.
- Create the first panel - chats, responses, templates, message history, basic mailing to your database.
- Submit and test approved templates for messages after 24 hours.
- Add logs, error handling, and Meta limitations to ensure the system is not fragile.

You will need access to Meta Business Manager, WABA or the ability to create WABA, a domain/server for webhooks, a list of user roles, and an example of the web service where messages need to be integrated.

I would like to clarify 2 points:
- Is your WhatsApp Business number already linked to Meta Business Manager or is it only working in the app on the phone for now?
- Does the web service already exist or does the first version of chats need to be created from scratch?

Similar cases from Ingello:
- https://business.ingello.com/vorfahr - AI and automation of communications, similar in logic to message processing and business processes.
- https://business.ingello.com/forma-crm - CRM and workflows for operators, similar to the part with chats, statuses, and templates.
- https://systems-fl.ingello.com - the main Ingello profile for automation projects and corporate systems. Expand

Budget: 200 USD Deadline: 7 days

Hello!

I fully understand your task. You are absolutely right to refuse "gray" methods (Baileys, Green API) — for a real business, this is a guaranteed risk of getting the number banned. We work exclusively "white" through the Meta Cloud API.

Regarding your main question — the coexistence mode: colleagues in the bids are arguing in vain. This mode officially exists in the Meta ecosystem, but it has a number of strict limitations that need to be known "upfront":

Eligibility: The ability for the application and API to work in parallel depends on the type of number, the country of registration, and the operating system your WhatsApp Business App is currently running on (Android/iOS).

Limits on broadcasts: In coexistence mode, Meta artificially lowers the bandwidth (Tier limits) for mass broadcasts to protect users from spam. If you need thousands of broadcasts per day, coexistence may become a bottleneck.

Step-by-step plan on how we will proceed:
Step 1 (Audit): First, we will audit your Meta Business Manager and check the number for eligibility for coexistence through Embedded Signup, so as not to break anything in the current application.
Step 2 (Backend in Python): I will set up a server (FastAPI/Django) for instant receipt of webhooks from Meta. We will implement tracking of all statuses (sent, delivered, read, failed).
Step 3 (Templates and Interface): We will set up Approved Templates (Meta templates) to bypass the 24-hour window and assemble the first simple version of the panel for messaging and broadcasts to your database.

I am ready to take on the audit and check your number. Please let me know if your Meta Business Manager is already verified and what operating system (Android or iOS) your phone is currently running on? Expand

Budget: 200 USD Deadline: 7 days

Hello!

I have experience working with the WhatsApp API.
I am ready to complete the assigned task.

I suggest we discuss the details in private messages.

Budget: 250 USD Deadline: 7 days

Hello!

I work with the official WhatsApp Cloud API — the task is clear, and I will say right away: you are correct in wanting the official route, not gray QR/Baileys/Green API (Meta bans them, and it's a risk for a business number). We will do it the right way through WABA + Cloud API.

I suggest breaking it down into two logical steps so that you don’t pay blindly:

Step 1 — coexistence check + preparation. Coexistence (the number remains in the WhatsApp Business App and works in parallel through the API) is a real official feature of Meta, but it is relatively new, and it has requirements for the number/account. Therefore, I will first check the eligibility of your number and explain what accesses and documents are needed for Meta (Business verification, WABA). This way, we will ensure that your current working number can be connected without disrupting what is already working on the phone.

Step 2 — connection and first version. After the check:

- I will connect WABA + Cloud API to your number;
- set up incoming messages (webhooks);
- sending from the web service;
- statuses (sent / delivered / read / error);
- approved templates for messages after the 24-hour window (I will create + submit for Meta moderation);
- a simple first version: chats, responses to clients, templates, mailing to your database.

From experience: I work with Cloud API (webhooks, sending, statuses, templates), this is a standard integration for me. Coexistence as a feature is newer, so I start with checking availability for your number — honestly, without "100% I will connect" until the Meta requirements are checked.

Where shall we start — will you give access to Meta Business / the number for the coexistence check, and I will tell you if your case passes? Expand

Budget: 200 USD Deadline: 5 days

Good day!

I have worked with Meta Cloud API / WABA.

An important point regarding your task:
Official coexistence (the number simultaneously in the app and API) — Meta has officially not supported this scheme since 2022.

What is actually possible:
- Connect the number to WABA via Cloud API
- Use different numbers for the app and API
- Or fully migrate the number to the API

I am ready to first check the status of your number in Meta Business Manager and provide an accurate answer on what is possible in your case.

Cost of the check: free
Connection: 200 USD
Timeline: 3-5 days Expand

Budget: 250 USD Deadline: 5 days

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

Budget: 100 USD Deadline: 5 days

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?

Budget: 100 USD Deadline: 7 days

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