WhatsApp messages directly with Meta’s WhatsApp Business Platform (Cloud API)
Short answer: yes. You can send WhatsApp messages directly with Meta’s WhatsApp Business Platform (Cloud API) from your app/website—no BSP required. Meta hosts the API, you integrate via Graph API, and you pay Meta’s published message rates. (Facebook for Developers, WhatsApp Business)
How “direct with Meta” works (at a glance)
- API option: Cloud API (hosted by Meta)—no server hosting by you; just call the endpoints from your backend and handle webhooks. (There’s also an on-prem API, but Cloud API is the recommended path.) (Facebook for Developers)
- Pricing: From July 1, 2025 Meta bills per delivered message, priced by category (Marketing, Utility, Authentication, Service) and country. Service messages and utility replies within the customer-service window are free; Marketing/Authentication/most Utility are charged. Also, messages are free for 72 hours after someone contacts you via a Click-to-WhatsApp ad or Facebook Page CTA. (WhatsApp Business)
- Limits & quality: Phone numbers have messaging limits and throughput rules; quality rating affects scale. (Example: per-recipient rate limits; tiered messaging limits.) (Facebook for Developers)
- Policies: You must follow Meta’s Business Messaging Policy (consent/opt-in, template rules, etc.). (WhatsApp Business)
Direct Meta vs. using a BSP (partner)
| Decision factor | Direct with Meta (Cloud API) | Through a BSP |
|---|
| Cost | Pay Meta’s per-message rates (some categories free as above). No BSP markup. (WhatsApp Business) | Often Meta rates + platform fees (varies by vendor/features). |
| Time to integrate | You build: backend calls, webhooks, template mgmt, inbox/CRM if needed. | Faster if you want UI, inbox, automations, analytics out-of-the-box. |
| Control & portability | Full control; easy to switch tools; no vendor lock-in. | Convenience; vendor tooling can speed ops but adds dependency. |
| Support & tooling | You rely on docs + your team’s ops. (WhatsApp Business) | Vendor support, campaign tools, QA, compliance help. |
| Onboarding | Create WABA, verify business & display name, add numbers, set webhooks, approve templates. | Often a guided “embedded signup” flow + dashboards. (Facebook for Developers) |
When going direct makes sense
- You have engineering resources, want lowest platform overhead, and can build a simple message/OTP service.
- You already run your own CRM/CS tooling (or don’t need one).
Setup checklist (direct with Meta)
- Create a Meta app and add WhatsApp product; create/attach a WhatsApp Business Account (WABA). (Facebook for Developers)
- Verify your business in Business Manager and approve a display name for the phone number. (Facebook for Developers)
- Add a phone number (new or onboard an existing Business App number via Embedded Signup / coexistence). (Facebook for Developers)
- Generate a permanent access token (system user), and set your webhook endpoint for message/status callbacks. (Facebook for Developers)
- Register message templates (categories: Marketing, Utility, Authentication) and wait for approval. (Facebook for Developers)
- Go live: send messages from your backend; respect rate limits, messaging limits, and policy. (Facebook for Developers, WhatsApp Business)
Cost notes you’ll care about
Minimal architecture (recommended)
- Your app/website ➜ your backend ➜ Meta Cloud API (Graph API).
- Keep tokens/credentials server-side only.
- Consume webhooks to track delivery, reads, and template status. (Facebook for Developers)
If you want, I can sketch a tiny Node/PHP code block and a DB schema for messages (status, retries, template IDs) so your team can wire this into Motoshare quickly—plus a cost model for India vs. your other markets using Meta’s live rate cards. (WhatsApp Business)