Meta Cloud API Direct or Through a Provider? An Honest Comparison

Someone always points out that Meta's Cloud API is free to use and that providers are "just a wrapper". Both statements are true, and the conclusion people draw from them is usually wrong.

We make one of those providers, so read this with that in mind. We have also watched enough businesses go direct and come back to describe the trade honestly rather than pretend direct is a bad idea — for some companies it is clearly the right one.

What "direct" actually gives you

Meta's Cloud API is exactly that: an API. You get endpoints to send a message, receive a webhook when one arrives, submit a template for approval, and manage your phone number. Meta hosts it, there is no server to run, and there is no platform fee.

What you do not get is everything a business actually uses day to day:

• A shared inbox your team can work from
• Assignment, so two agents do not answer the same customer
• Template management and submission tracking
• Campaign scheduling, segmentation and opt-out handling
• A chatbot builder
• Reporting on delivery, reads, replies and agent performance
• Someone to call when a message stops going out

Every one of those is software you now build and maintain. That is the actual choice — not "pay a fee or do not", but "buy this software or build it".

The cost comparison people get wrong

Meta's per-message charge is identical either way. For users in India that is ₹1.09 for a marketing message and ₹0.145 for utility, authentication and service messages, with the first 1,000 service messages free per number each month. Going direct does not reduce this by a paisa — it only removes the platform fee on top.

So the question is whether the platform fee is less than what building and running the equivalent costs you. For a small Indian business the honest arithmetic usually looks like this:

• Platform route: a fixed monthly fee, working from day one, with support.
• Direct route: developer time to build the inbox and campaign tooling, then ongoing time for API version upgrades, webhook reliability, template failures and whatever breaks at 9 pm during a campaign.

Even a modest internal build is several weeks of developer time, and the maintenance never stops. Against a platform fee in the low thousands per month, direct rarely wins on cost alone for a team of under twenty people. What platforms actually charge is compared in what every WhatsApp CRM costs in India.

When direct is genuinely the right call

Three situations where we would tell you to go direct without hesitation:

1. You are a software product and messaging is a feature inside it. If notifications belong in your own app's workflow, a third-party inbox is in the way, not helping.
2. You have real engineering capacity and very high volume. At large scale the platform fee becomes material and you have the team to absorb the maintenance.
3. Your requirement is narrow and machine-driven. One-way OTPs or order alerts, no humans replying, no campaigns. That is a few hundred lines of code and genuinely does not need a platform.

When a provider is the right call

1. People, not just systems, will reply to customers. The moment a human needs to answer, you need an inbox, assignment and history — and that is most of the product.
2. You want to run campaigns. Segmentation, scheduling, opt-out handling and reporting are where most of the hidden work lives.
3. You have no developer, or your developer has better things to do. Opportunity cost is the real number, not the fee.
4. You need it working this week. Direct is a project; a platform is a setup.

The hybrid most teams end up with

This is the part nobody mentions, and it is what we see most often at scale: use a provider for the human side — inbox, campaigns, templates — and use the provider's own API for the automated side, so your systems trigger messages while your team still has a place to work. You get the tooling without losing programmability, and you do not maintain two stacks.

If you do go direct, the setup path is the same as any other: business verification, display name review, template approval. It is covered step by step in how to set up the WhatsApp Business API.

The one thing to get right either way

Whichever route you choose, insist that your WhatsApp Business Account lives inside your own Meta Business Manager, with any provider added as a partner. This single decision determines whether you can change your mind later.

• Your Business Manager, provider as partner — your number, your templates, your quality history. Switching is a technical task.
• Provider's Business Manager — moving becomes their decision, not yours.

Ask it in exactly those words before signing anything. More on what else to check in who owns your WhatsApp data and number.

The short version

Direct is not cheaper, it is unbundled. You stop paying a fee and start paying in engineering time. If messaging is a feature of your product, or your use is purely automated at high volume, unbundling makes sense. If people will reply to customers and you want campaigns, buy the software — and keep the Business Manager in your own name so the choice stays reversible.

What actually breaks when you go direct

The build is the part people estimate. The maintenance is the part that decides whether direct was the right call. These are the recurring items teams running direct deal with:

• API versions expire. Meta releases Graph API versions regularly and retires old ones on a schedule. Code that worked for a year stops working on a date somebody has to be tracking. A provider absorbs this; direct means you own the calendar.
• Webhooks are not guaranteed to be convenient. They retry, they duplicate, and they arrive out of order. If your handler is not idempotent you will double-charge, double-reply or lose a message — and you usually discover this during a busy hour.
• Template state drifts. Templates get approved, rejected, paused for quality or disabled. Something has to reconcile Meta's view with yours, or a campaign fires against a template that no longer exists.
• Rate limits and tier changes. Your messaging limit moves as your quality rating moves. Code that sends blindly will start failing mid-campaign unless it reads the limit and backs off — the mechanics are in quality rating and messaging limits.
• Media handling. Uploading, caching and re-using media IDs, and dealing with expiry, is more work than it sounds.
• Nobody to escalate to. When messages stop going out at 9 pm, direct means reading status pages and your own logs. There is no support line that knows your account.

None of this is hard for a competent developer. All of it is ongoing, and that is the honest cost of direct: not the build, the decade.

A question that settles it quickly

Ask yourself: if this integration breaks on a Saturday during a campaign, who fixes it, and how fast?

If the answer is "our developer, within the hour, and they already know this code" — direct is viable. If it is "we would raise it with someone on Monday", you want a platform, because the cost of a quiet outage during your busiest window is larger than any fee you were saving. That one question predicts the outcome better than any cost spreadsheet we have seen.

Frequently Asked Questions

Is it cheaper to use Meta's Cloud API directly?

On the invoice, yes — you pay Meta's per-message rate with no platform fee. In total cost, usually not for a small team, because you are now building and maintaining the inbox, templates, campaigns, webhooks and reporting a provider gives you. Direct makes sense when you have developers and a product to embed messaging into.

What do you lose by going direct?

Everything that is not the API itself: a shared team inbox, agent assignment, template management, campaign scheduling, segmentation, chatbot building, analytics, and support when something breaks. Meta gives you the pipe; the product around the pipe is what a provider sells.

Can we move from a provider to direct later?

Yes, and what makes it possible is having your WhatsApp Business Account inside your own Meta Business Manager with the provider added as a partner. If it sits inside the provider's Business Manager, moving becomes their decision rather than yours. Check this before you sign.

Does going direct change the per-message price?

No. Meta's rates are the same whichever route you take — in India, ₹1.09 for marketing and ₹0.145 for utility, authentication and service messages, with 1,000 free service messages per number each month. Only the platform fee on top differs, and some providers add a markup on Meta's rate, which is worth asking about in writing.

How long does a direct integration take to build?

Sending a message takes an afternoon. Building something a team can actually work in — inbox, assignment, templates, campaigns, opt-outs, reporting — is several weeks of developer time, and then it needs maintaining as the API changes. Plan against the second number, not the first.