Coexistence Setup for WhatsApp Cloud API

@kamran2012

Hello there, I will set up your Meta Tech Provider account, build the Embedded Signup flow with `featureType: whatsapp_business_app_onboarding` on the launch configuration, and onboard all six UAE numbers to coexistence so your reps never leave the Business app. Screening answers: 1) I onboarded a multi-rep sales team (five numbers) to coexistence by running Embedded Signup with the coexistence feature type, exchanging tokens server-side, then syncing history within the 24-hour window. 2) `featureType: whatsapp_business_app_onboarding` set on the Embedded Signup launch configuration object. 3) Subscribe to `messages`, `smb_message_echoes`, `history`, and `smb_app_state_sync`. The `smb_message_echoes` field carries rep-sent messages. 4) You have 24 hours to call the history sync endpoint. Looking forward to talking through the details. Kamran

@diektech

Hi, This is Elias from Miami. I checked the details and understand you need a direct Meta-owned WhatsApp Cloud API setup with Tech Provider approval, Embedded Signup Coexistence, and webhooks mirrored to your self-hosted backend. The real challenge here is not only webhook coding, but getting App Review, coexistence onboarding, token exchange, history sync, and message echoes handled correctly. Screening answers: 1 – I’ve worked with direct WhatsApp Cloud API/Embedded Signup flows; I’d validate coexistence first on one existing app number before rolling out all reps. 2 – Coexistence is enabled with featureType: whatsapp_business_app_onboarding in the Embedded Signup launch configuration. 3 – Required fields include messages, smb_message_echoes, history, and smb_app_state_sync. smb_message_echoes carries messages sent by reps from the WhatsApp Business app. 4 – History sync must be triggered within 24 hours after onboarding; if missed, that one-time sync payload is not available again normally. 5 – App Review usually needs business verification, permission justification, screencast walkthrough, use-case explanation, data handling details, and working demo flow. I’d approach this by setting up Tech Provider/App Review first, then proving one number end-to-end, and only after approval onboarding the remaining numbers with documentation and handover. Looking forward to hearing from you.

@seefattechnologi

OKAY------Got the Scope of work------------->>Coexistence Setup for WhatsApp Cloud API I will deliver exactly what you need with high-quality, clean, and scalable solutions. I have rich expereince similar projects for my clients before. As an experienced Full Stack Developer, I am sure you'll be impressed with both my work quality and commitment.  Please ping me to get started and achieve outstanding results. Thanks!!

@DrSyafiq

You are not asking for a reseller WhatsApp dashboard; you need direct Meta Tech Provider setup with Embedded Signup and Coexistence so existing sales reps keep using the WhatsApp Business app while messages mirror into your own backend. I would handle this as a controlled Meta/API implementation: verify business/app readiness, map the coexistence onboarding flow, implement webhook handling, persist message/contact events, and document the exact approval and deployment steps. For this project I would focus on: - Meta Business/App Review readiness for whatsapp_business_messaging and management access - Embedded Signup with Coexistence enabled for the existing numbers - Self-hosted webhook backend, logging, retries, monitoring, and CRM-ready data model - Clear admin/test checklist so reps can confirm app usage remains unchanged If useful, I can first map the approval/onboarding sequence and the webhook payloads we need to store before coding. Best, Dr. Syafiq

@ZohaibRoy

⭐⭐⭐⭐⭐ WhatsApp Cloud API Integration & Coexistence Setup Expert ❇️ Hi My Friend, I hope you are doing well. I've reviewed your project requirements and see you are looking for a WhatsApp Cloud API Tech Provider. Look no further; Zohaib is here to assist you! My team has successfully completed 50+ similar projects for WhatsApp integrations. I will ensure your existing numbers are connected to the Cloud API while keeping your current setup intact. ➡️ Why Me? I can easily do your WhatsApp Cloud API setup as I have 5 years of experience in API integration, specifically with WhatsApp. My expertise includes business verification, webhook configuration, and message synchronization. Additionally, I have a strong grip on server-side coding for token exchanges and can guide you through the entire process. ➡️ Let's have a quick chat to discuss your project in detail and let me show you samples of my previous work. Looking forward to discussing with you! ➡️ Skills & Experience: ✅ WhatsApp Cloud API Integration ✅ Embedded Signup Implementation ✅ Meta Business Verification ✅ Webhook Configuration ✅ Message Synchronization ✅ App Review Process ✅ Server-Side Coding ✅ API Documentation ✅ n8n Automation ✅ Problem Solving ✅ Client Guidance ✅ Technical Support Waiting for your response! Best Regards, Zohaib

@mubeenm5026

As an accomplished software development company with a wealth of experience in API Development and Linux, especially since my last project involved LinkedIn API integration, I am confident I am the perfect fit for your needs. At Web Crest, we don't just develop applications - we develop solutions to real-world problems. Your focus on implementing Meta Tech Provider and Embedded Signup coexistence setup aligns perfectly with what we bring to the table. We have set up numerous complete systems from scratch and this situation is no different. Crucially, I understand that 'the devil is in the details'. Following your precise scope of work, I will meticulously guide and configure your Meta Business account & admin access, submit the App Review with top-notch justifications while providing effective screen-recording walkthroughs. Being proficient in Node.js, Python and experienced in REST APIs development & GraphQL which also encompasses delivering webhook subscriptions — `messages`, `smb_message_echoes`, `history`, `smb_app_state_sync' to a self-hosted endpoint can guarantee swift integration of your system.

@myGigs

Good evening! I'll guide you through the full Meta Tech Provider setup including business verification, App Review submissions for whatsapp_business_messaging and whatsapp_business_management, and the Embedded Signup coexistence flow with featureType: whatsapp_business_app_onboarding, then onboard all six UAE numbers to the Cloud API without removing them from the WhatsApp Business app, configure webhooks to capture inbound messages, smb_message_echoes, and the one-shot history sync payloads on your self-hosted VPS endpoint. Any specific deadline I should work around?

@codefusion53

Hi I can implement WhatsApp Cloud API coexistence with Embedded Signup as your self hosted integration, built directly on Meta workflows and owned by your Meta Business infrastructure, not via a BSP dashboard. My approach is: Tech Provider onboarding in Meta App Dashboard, Meta Business verification and App Review for whatsapp_business_messaging and whatsapp_business_management, then Embedded Signup launch with the coexistence flag to enable onboarding where the WhatsApp Business app remains active. I will build the server side token exchange service, the Embedded Signup page endpoint, and the webhook receiver that validates signatures and persists payloads for inbound messages plus smb_message_echoes and the smb_app_state_sync and history one shot sync events. I will prove the chain on 1 development number first, including template and session sending from the API, then expand to all ~6 numbers after App Review approval. Deliverables include a Git repository with source code, n8n friendly webhook setup, environment templates, and a step by step runbook with what to record for screen recordings and how to onboard additional numbers later. Best, Justin

@samarhabib

Greetings, I'm a full stack developer with 10+ years of experience, with direct, hands-on work building WhatsApp Cloud API integrations on Meta's own infrastructure — not through BSP dashboards like Wati or Twilio. I've implemented Embedded Signup, Tech Provider onboarding, and Coexistence flows exactly like the one you're describing. Why work with me? ★ Proven track record: 75 successful projects with 5-star reviews ★ Expertise in Node.js, Angular, React, Express, Python, Django, Flask, PHP, WordPress, Laravel, Codeigniter and more — plus n8n for the webhook/automation side you're already running ★ Responsive, deadline-focused, and committed to results ★ 3 months of free post-launch support I'm comfortable with the milestone structure you proposed (M1–M4) and can give you a price per milestone once we talk through the current state of your Meta Business account and number(s). Let's schedule a quick chat to discuss timelines, the App Review queue, and launch goals. I'm confident I can bring your vision to life. Best regards, Samar H.

@sekai1116

With over a decade of experience in web development and a strong background in API development and integration, I am the ideal freelancer to help you achieve your goals with the WhatsApp Cloud API and Meta's Coexistence feature. My expertise in building scalable backend systems and well-structured APIs aligns perfectly with your project's needs. Not only can I guide you through the Meta Business verification and Tech Provider setup, but I can also steer you through the App Review process with ease. Additionally, my extensive experience with SaaS platforms and subscription-based services can prove invaluable for the second phase of your project, which involves logging, monitoring, and CRM integration. From complex web systems to marketplaces and booking systems, I have successfully delivered various applications that underscore growth-focused digital products - exactly what your project requires. In essence, no matter how intricate or manifold the different parts of this engagement are, I'm confident that my skill-set encompasses them all. Lastly, truly understanding the significance of a seamless handoff after project completion; I commit to providing clean documentation and source code upon project completion whilst ensuring that you have a full grasp on its function and how to build upon it for future system expansion. I'm excited about the opportunity to help unleash the full potential of WhatsApp Cloud API for your business.

@techsty2014

Hi there, We will set up your Meta Tech Provider account, implement the Embedded Signup coexistence flow, and onboard all six UAE numbers to the Cloud API while keeping the Business app fully active. To your screening questions: 1) We onboarded a sales team's existing numbers via coexistence, mirroring all traffic to a self-hosted backend without disrupting daily app usage. 2) You set `featureType: whatsapp_business_app_onboarding` on the launch configuration object. 3) Subscribe to `messages`, `smb_message_echoes`, `history`, and `smb_app_state_sync`. The `smb_message_echoes` field carries rep-sent messages. 4) You have 24 hours to sync history. Miss it and the payload is lost permanently. 5) Yes. Meta required permission justifications, a screen recording walkthrough of the integration, and a privacy policy URL. Looking forward to your response. Best regards, Faizan

@TechWagger2026

As an accomplished web and mobile app developer with a strong background in CRM solutions - and customization - my experience aligns impeccably with your project requirements. With over 14 years of experience and more than 400+ projects under my belt, I can confidently affirm my ability to provide full-stack development encompassing the Meta setup and Embedded Signup needed for your Coexistence venture. I'm also well-versed in API integration, Linux, MySQL, and overall system administration. Notably, I have successfully integrated several third-party solutions into business systems: an expertise that qualifies me for this project. This ensures that your existing sales team can continue using WhatsApp Business app as they do now but with added functionalities achieved through WhatsApp Cloud API. My focus will be to establish a seamless and robust coexistence set up between Meta's infrastructure and your self-hosted backend. When you choose me for this project, you're not just acquiring top-notch technical skills; you're also gaining a committed partner dedicated to delivering customer satisfaction at every stage of the project. I believe our collaboration will lay the groundwork for a solid technical infrastructure that facilitates smooth logging, monitoring, and future CRM integration – just as you envision it! Let's get started on advancing your sales communication framework while maintaining user-familiarity with WhatsApp!

@wasifmuneer

Hi there, I’d be happy to discuss your project—feel free to start a chat anytime. I’m a full-stack developer with solid experience building scalable web and desktop applications, and I’m confident I can deliver your project efficiently and on time. I also have strong exposure to modern technologies including Web3 concepts, DevOps practices, and automation. I’m a Kubernetes enthusiast with hands-on experience using Docker containers and deploying applications on Linux servers. My expertise includes: MERN / MEAN Stack (development + team management) .NET Core APIs with Angular, including D3.js data visualizations Azure Logic Apps, SharePoint, and workflow automation (PowerApps familiarity) Salesforce development with Apex, Visualforce, and integrations via .NET APIs DevOps basics, containerization, and application hosting on Linux Automation workflows and AI-based tools to improve efficiency I bring a problem-solving mindset and full project lifecycle experience—from development to deployment. Looking forward to hearing from you. Thank you!

@Olywebart

Hello there, Your need to enable coexistence between WhatsApp Business app and Cloud API, with seamless message mirroring to your self-hosted backend, is clearly pivotal for your UAE sales team’s workflow. I can help establish your business as a Meta Tech Provider and implement the Embedded Signup coexistence flow as required. I’ve managed integrations directly with Meta’s platform for WhatsApp Cloud API, handling advanced permissions via Meta App Review and configuring webhook subscriptions for inbound, echo, and history message streams. My approach: 1) Guide your Meta Business verification and prepare the App Review with detailed permissions and scripts, 2) Develop and host the Embedded Signup page with secure token exchange and orchestration of onboarding sync within the 24-hour window, 3) Validate webhook delivery and message sending on one test number before scaling to all your reps. Let's start with setting up a working coexistence flow on your first number and get your Meta app review submission ready promptly. A short call to align on your VPS environment and n8n webhook setup might help streamline progress. Could you clarify your preferred hosting approach for the Embedded Signup flow: fully self-hosted on your VPS or partially using Meta's Hosted Embedded Signup? Best regards, Anatolie

@chiragpipal

⚠️ If you're not happy, you don’t pay. ⚠️ Hi there, Thank you for sharing the detailed project brief. I can build your project using the WhatsApp Cloud API with a premium, scalable, and performance-optimized design. I will deliver: • Setting up as a Meta Tech Provider • Implementing Embedded Signup with Coexistence • Onboarding existing sales-rep numbers to the Cloud API • Configuring webhooks and message stream delivery • Enabling the ability to send messages via the API • Comprehensive documentation and handover support You will also receive guidance, documentation, and support clarity beyond the project scope. I am confident I can execute your vision professionally and efficiently. Looking forward to discussing timeline and next steps. Best regards, Chirag.

@saadrizwan97

Hi, We can help set up WhatsApp Cloud API directly through Meta, not via Wati, Twilio, or 360dialog. We can support Tech Provider setup, App Review, Embedded Signup with coexistence, webhook configuration, token exchange, one-number testing, and rollout for all 6 UAE numbers. Key answers: Coexistence is enabled using featureType: whatsapp_business_app_onboarding in the Embedded Signup config. Required webhook fields include messages, smb_message_echoes, history, and smb_app_state_sync. Rep-sent WhatsApp Business app messages come through smb_message_echoes. History sync must be triggered within 24 hours after onboarding, otherwise the one-time sync can be missed. We can work milestone-based, provide source code, documentation, and a handover call.

@mayr81

Got it, this is exactly the kind of Meta-native WhatsApp Cloud API build-up where details matter (and where copy-paste “BSP dashboard” steps usually fail). I’ll help you set up your business as a Meta Tech Provider, then implement Embedded Signup for coexistence so your reps keep using the WhatsApp Business app while every inbound, `smb_message_echoes`, and onboarding history/sync payload gets mirrored into your self-hosted logging stack. Approach: 1) Meta verification + Partner Solution configuration + App Review package for the two advanced permissions. 2) Embedded Signup coexistence onboarding (`featureType: whatsapp_business_app_onboarding`) with token exchange and launch config. 3) Orchestrate onboarding + the 24-hour history-sync window and verify webhook payloads for messages + echoes. 4) Prove the full chain on one UAE development number first, then scale to the remaining ~6 after approval. Deliverables: source in a Git repo (Embedded Signup page + token-exchange service + webhook handler), documentation, and a smooth handover to operate it yourself, no “mystery dashboard magic,” just your infrastructure doing the job.

@FizzaNadeemK

Hi, at your scale, WhatsApp Coexistence is about extending live sales conversations into Cloud API without disrupting the reps already working inside the WhatsApp Business app. I have implemented Embedded Signup–based coexistence onboarding for a multi-rep sales setup where existing WhatsApp Business app numbers were connected to Cloud API so conversations stayed uninterrupted while messages were mirrored to a backend, including per-number onboarding flow and token exchange orchestration. In Embedded Signup, coexistence is enabled via the featureType: whatsapp_business_app_onboarding on the launch configuration object, webhooks must subscribe to messages, smb_message_echoes, history, and smb_app_state_sync where echoes carries rep-sent messages, the history sync must be completed within the 24-hour window or full backfill is no longer possible, and App Review for whatsapp_business_messaging and whatsapp_business_management requires business verification plus a screencast and clear permission justification. I would set up the Tech Provider app structure, guide the App Review submission, implement the Embedded Signup + server-side token exchange, and validate end-to-end messaging on one number before scaling onboarding to the remaining lines after approval. For App Review, did you already prepare the product walkthrough and data handling explanation, or would you want me to script the exact recording flow for your team to submit? Best regards, Fizza Nadeem K

@abhishek060

Hi! I've reviewed your requirements and understand you're looking for a direct Meta-based solution rather than a BSP, while ensuring your existing WhatsApp Business numbers continue working seamlessly through the Coexistence feature. I can help you implement WhatsApp Cloud API directly through Meta, including Embedded Signup, Tech Provider onboarding, Coexistence, App Review, and webhook integration on your self-hosted infrastructure. A few questions: 1. Have you already completed Meta Business Verification, or will that be part of Phase 1? 2. Is your n8n environment already configured to receive webhooks, or should that be included in the implementation? 3. Are all six numbers under the same WhatsApp Business Account (WABA), or will they require separate onboarding? I've worked with WhatsApp Cloud API integrations, webhook handling, authentication flows, and Meta platform integrations. If we're aligned on the scope, I'd be happy to discuss the implementation approach, milestone breakdown, and a realistic timeline based on Meta's review process.