Reference · built on requestConnectorMessaging & notifications

WhatsApp Business Platform

Customer messaging on WhatsApp through the Cloud API: templates, session replies, media, and webhook status events.

Request accessPricing ↗

About

The WhatsApp Business Platform is how a company messages customers on WhatsApp. The Cloud API is hosted by Meta and built on the Graph API. You hold a business portfolio, a WhatsApp Business Account inside it, and a business phone number, and you call the API with an access token from your Meta app. Outside a customer service window only approved templates can be sent, in the marketing, utility, or authentication category. Inbound messages, delivery and read status, and template status changes arrive as webhooks.

Through Fibric, an operator watches those webhooks and proposes a template send or a session reply for a person to approve, with the delivery status attached to the customer record.

This is a reference listing. It documents what Fibric would read from WhatsApp Business Platform and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Inbound customer messages through the messages webhook field: text, media, and interactive replies
  • Status updates for each message the business sent, delivered as webhook payloads
  • Template review outcomes through the message_template_status_update webhook
  • The customer service window that opens for 24 hours after a customer's message; outside it only templates may go
  • Template status, where only APPROVED templates can be sent and rejected, paused, or disabled ones cannot

Proposed actions

  • Target capability: propose sending an approved template message outside the customer service window
  • Target capability: propose a text, media, or interactive reply inside the 24 hour customer service window
  • Target capability: propose a new utility template through the Message Templates API, which is reviewed automatically on creation

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Answer where-is-my-order on WhatsApp

    An inbound question about an order is matched to the shipment and a session reply is drafted with the current status. A person approves it while the customer service window is open.

    With WISMO Deflection

  • Backorder notice by utility template

    When an item slips, the operator proposes an approved utility template to each affected customer, one per order. Delivery and read status return by webhook and land on the order record.

    With Backorder Notice, Missed Delivery

  • Reminders that respect the messaging tier

    Appointment reminders queue against the phone number's tier and the one-per-6-seconds pair rate, so a batch does not exhaust the limit. A person approves the batch, not each message.

    With Appointment Reminder

Requirements

  • A Meta developer account and a Meta app created with the WhatsApp use case
  • A business portfolio, a WhatsApp Business Account, and a business phone number registered to it
  • A system user token with business_management, whatsapp_business_messaging, and whatsapp_business_management
  • An HTTPS endpoint subscribed to the messages webhook field
  • Templates in the marketing, utility, or authentication category that have passed review
Authentication
A system user access token from your Meta app, carrying whatsapp_business_messaging and whatsapp_business_management, sent as a Graph API bearer token.

Limits

  • A new portfolio starts at 250 unique recipients per 24 hours; the tier rises to 2,000, 10,000, 100,000, then unlimited
  • A business phone number sends up to 80 messages per second by default
  • One message every 6 seconds to the same WhatsApp user, with a burst of up to 45 in 6 seconds
  • Free-form replies need a customer message first; beyond the window only approved templates are accepted

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request WhatsApp Business Platform ↗

Questions and answers

What can be sent outside the customer service window?
Only template messages. Templates are built in advance in the marketing, utility, or authentication category and are reviewed automatically on creation or edit. Once a template is APPROVED you can send it; rejected, paused, or disabled templates cannot be sent.
How does the messaging limit grow?
A new portfolio can reach 250 unique recipients in 24 hours. Business verification, or 2,000 delivered template messages to unique numbers within 30 days at high quality, moves it to 2,000. After that it rises one level within 6 hours when you use at least half your limit over 7 days with high-quality messages.
How do inbound messages and delivery receipts reach Fibric?
Through webhooks. You subscribe an HTTPS endpoint to the messages field; Meta posts JSON for each inbound message and each status change on messages you sent. If the endpoint does not return HTTP 200, Meta retries with decreasing frequency for up to 7 days.
Ask about WhatsApp Business Platform

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with WhatsApp Business Platform through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy