Official WhatsApp Cloud API Platform for Business
Connect an authorised WhatsApp Business Account through Meta Embedded Signup, then manage customer conversations, teams, templates, campaigns, automation, analytics and integrations from BotLinkd.
BotLinkd is an independent platform and is not owned or operated by Meta.
No QR-code browser automation. The connection uses official business assets, permissions, credentials and events.
Cloud API explained
Official infrastructure for programmable WhatsApp business messaging
The WhatsApp Business Platform Cloud API allows an authorised business to send and receive supported WhatsApp messages programmatically. Meta hosts the Cloud API infrastructure, while BotLinkd provides the business-facing workspace, onboarding, conversation tools and integrations.
Incoming messages and delivery events are processed through webhooks. Outbound messaging follows current WhatsApp rules, including approved templates where required.
Official business authorisation
The business grants access to the relevant Meta and WhatsApp assets through the approved onboarding flow.
Event-driven communication
Webhooks deliver supported inbound messages, delivery updates and account events to the connected platform.
Business workflow layer
BotLinkd adds team access, contacts, templates, campaigns, automation, analytics and external-system connections.
What BotLinkd adds to Cloud API
Turn infrastructure into an operating customer-communication platform
Cloud API provides the official messaging foundation. BotLinkd adds the interfaces and controls teams use for daily business operations.
Two-way business messaging
Receive customer messages through official webhooks and send supported replies, templates and media from one BotLinkd workspace.
Multi-agent shared inbox
Let authorised sales, support and operations users manage conversations under one connected business number.
Approved message templates
Create and submit Marketing, Utility and Authentication templates with supported variables, media and buttons.
Campaigns and scheduling
Send approved template campaigns to opted-in contacts and schedule supported messages according to account limits and policy.
Automation and routing
Use quick replies, auto replies, workflow rules and supported conversation routing to reduce repetitive manual work.
AI with human handover
Add optional AI assistance while retaining contact-level pause, platform-wide pause and direct human-agent control.
Delivery events and analytics
Track supported message states, campaign delivery events and operational communication performance.
APIs and webhooks
Connect websites, CRMs, commerce systems and internal workflows using protected credentials and real-time events.
Meta Embedded Signup journey
Connect the business assets, number and operating workflow
The exact screens and eligibility checks can vary, but an official connection normally follows this business-authorised path.
-
01
Prepare the Meta business assets
Use an authorised Meta business portfolio and confirm the business, administrator access and intended WhatsApp use case.
-
02
Start Meta Embedded Signup
Sign in to Meta from the BotLinkd onboarding flow and select or create the required WhatsApp Business Account assets.
-
03
Authorise the phone number
Select an eligible number, complete the required verification and confirm whether coexistence or migration applies.
-
04
Connect permissions and webhooks
Authorise the required platform permissions so BotLinkd can process supported messages, statuses and account events.
-
05
Configure the operating workflow
Add team members, templates, contacts, automations, campaigns, integrations and human handover controls.
Setup time is not fixed. It depends on administrator access, business assets, number eligibility, verification requirements and Meta account review.
Existing WhatsApp Business app numbers
Coexistence may let an eligible number use the app and Cloud API
Connecting Cloud API does not always require deleting the existing WhatsApp Business app account. Meta supports an official coexistence onboarding path for eligible businesses and numbers.
In supported cases, recent chat history can be synchronised and messages can be mirrored between the WhatsApp Business app and Cloud API. Where coexistence is unavailable or unsuitable, a migration may still be needed.
Do not delete, migrate or re-register an active production number before BotLinkd confirms the current eligibility and correct onboarding path.
Business use cases
Use Cloud API for structured customer communication
The strongest Cloud API implementations connect an approved messaging use case to teams, customer consent, templates and operational systems.
E-commerce operations
Order confirmations, shipping updates, delivery notices, customer questions and approved follow-up campaigns.
Customer support
Shared inbox handling, quick replies, media exchange, assignments, escalation and conversation visibility.
Sales and lead handling
Capture enquiries, qualify leads, route serious buyers and keep context available to authorised agents.
Appointments and reminders
Send approved confirmations, reminders, rescheduling prompts and service updates at the right time.
Multi-team communication
Coordinate sales, support, billing and operations without sharing one physical device or browser session.
System-triggered notifications
Use APIs and webhooks to trigger supported business messages from websites, CRMs, stores and internal tools.
Choose the right operating model
Cloud API compared with the WhatsApp Business app
These products serve different operating needs. Coexistence may be available for eligible businesses, so the choice is not always strictly one or the other.
| Area | Cloud API with BotLinkd | WhatsApp Business app |
|---|---|---|
| Connection model | Official WhatsApp Business Platform Cloud API, permissions and webhooks | Phone-based WhatsApp Business application |
| Team operations | Shared inboxes, roles, assignments and connected business systems | Primarily designed around app and linked-device usage |
| Automation | APIs, webhooks, templates, workflows and external integrations | Native app features with more limited system automation |
| Outbound initiation | Approved templates and applicable WhatsApp messaging rules | App-based conversations under the product’s own operating model |
| Operational scale | Designed for structured business messaging and system integration | Designed for direct small-business communication in the app |
| Number setup | Eligible numbers may use coexistence or require a migration path | Number remains registered to the WhatsApp Business app |
Templates and customer-service messaging
Match the message type to the conversation context
Supported free-form replies may be available within the applicable customer-service window after a customer message. Outside that context, approved templates are generally required to initiate or resume business communication.
- Marketing, Utility and Authentication template categories
- Supported variables, headers, footers, media and buttons
- Meta-controlled approval, categorisation and policy enforcement
- Business responsibility for opt-in and opt-out handling
Responsible platform use
Official API access does not remove business obligations
The business remains responsible for lawful customer data, valid opt-in, appropriate templates, accurate content, opt-out handling and messaging quality. Meta may restrict templates, numbers or accounts when platform requirements are not met.
Cloud API onboarding questions
Official WhatsApp Cloud API FAQs
These answers focus specifically on business assets, number eligibility, coexistence, Embedded Signup, webhooks and templates.
What exactly is the WhatsApp Business Platform Cloud API?
The Cloud API is Meta-hosted infrastructure that allows authorised businesses and technology providers to programmatically send and receive supported WhatsApp messages. It uses official business assets, permissions, access credentials and webhooks rather than automating a WhatsApp Web browser session.
What business assets are normally required before onboarding?
A business generally needs authorised access to the relevant Meta business portfolio, a WhatsApp Business Account or permission to create one, an eligible business phone number and administrator access for the Embedded Signup flow. Meta may also require business or number verification depending on the account and use case.
Can I connect a number that is already used in the WhatsApp Business app?
Possibly. Meta supports onboarding eligible WhatsApp Business app users through a coexistence flow in supported cases, allowing recent chat synchronisation and mirrored messages between the app and Cloud API. Where coexistence is not available or suitable, a migration path may be required. Eligibility depends on the number, country, account and current Meta configuration.
Do I always need to delete my WhatsApp Business app account first?
No. That is no longer a universal requirement. Eligible businesses may be able to use the official coexistence flow. Do not delete or migrate an active number until BotLinkd has checked the current eligibility and confirmed the correct onboarding path.
What happens during Meta Embedded Signup?
The authorised business user signs in to Meta, selects or creates the business and WhatsApp assets, chooses an eligible phone number, grants the requested permissions and completes the steps required to connect the account to the solution provider.
How are incoming customer messages delivered to BotLinkd?
Supported inbound messages and message-status events are delivered through official webhooks. BotLinkd uses those events to update the shared inbox, trigger configured workflows and expose relevant information to authorised users or connected systems.
When must a business use an approved template?
Approved templates are generally required when the business initiates or resumes a conversation outside the applicable customer-service window. The correct template category, pricing treatment and availability depend on the message purpose and current WhatsApp rules.
Does BotLinkd guarantee a specific setup time or template approval?
No. Setup timing depends on administrator readiness, number eligibility, Meta verification, business assets and account review. Template approval, rejection and categorisation are controlled by Meta, so BotLinkd cannot guarantee a fixed setup time or approval result.
Prepare the correct onboarding path
Connect your business to the official WhatsApp Cloud API
Start a BotLinkd account or ask the team to check your existing number, Meta assets, coexistence eligibility and intended messaging workflow.