Facebook API Pricing: Full Breakdown for 2026

Facebook API pricing is one of those search queries where the answer depends entirely on which API you mean. Meta runs four developer products under the same graph.facebook.com umbrella, and only one of them has a literal price tag. The Graph API, Marketing API, and Pages API are free. WhatsApp Cloud API charges per template message delivered. Most production use cases on all four also run into App Review, business verification, or permission review, and that approval cycle is where the real cost lives for most developers.

I run Blotato, which posts to Facebook Pages on behalf of thousands of businesses. So I’ve seen what the “free” stack actually charges teams in calendar time, what WhatsApp messaging adds up to on a real customer-service workload, and where the access tier quietly caps you. This guide walks through each product, with current numbers verified against Meta’s developer documentation in May 2026.

If you want Meta’s official reference, the Graph API documentation has it. If you want to know what to budget and how long things take in practice, read on.

Facebook API Pricing at a Glance (2026)

Access tier	Cost	Best for	Key friction
Graph API (Meta)	Free	Reading Page data, posting to Pages you manage	App Review, business verification, BUC rate limits
Marketing API (Meta)	Free	Managing ads, pulling Ads Insights	Marketing API Access Tier upgrade, ad-account rate limits
Pages API (Meta)	Free	Publishing posts to Facebook Pages	pages_manage_posts permission, Advanced Access for non-owned Pages
WhatsApp Cloud API	Pay-per-message	Customer messaging at scale	Template-message charges, business verification, per-country rates
RapidAPI third-party wrappers	$0 to $199/mo	Prototyping, low-volume scraping	Unofficial, no SLA, can break overnight

Three of the four Meta APIs cost zero dollars. The bill comes due in approval weeks, OAuth maintenance, and quota math. WhatsApp is the only one with a literal invoice, and even there the rules favor in-conversation, non-template messaging, which Meta provides for free.

Need to ship a Facebook posting integration today instead of in eight weeks? Start a free week of Blotato.

Free 7-day trial · Cancel anytime

What Changed in 2026

A few things shifted in the last twelve months that change the calculation if you’ve shipped on this stack before.

WhatsApp moved from per-conversation to per-message pricing on July 1, 2025. The old model billed you per 24-hour conversation window. The new model only charges you when a template message is delivered. Non-template messages inside an open customer service window are now free, with no monthly cap. If your post-2024 mental model of WhatsApp pricing still includes the words “service conversation” or “first 1,000 free,” it’s out of date.

Meta renamed Ads Management Standard Access to Marketing API Access Tier on May 4, 2026. The two-tier structure (limited access by default, full access after App Review) is preserved. No code changes required. The rename came with cleaner documentation of what each tier actually allows, including the explicit maintenance requirements on Full Access (500+ successful Marketing API calls in the last 15 days, error rate below 15% over the last 500 calls).

Graph API v25.0 shipped on February 18, 2026. The active version window as of mid-May 2026 runs from v19.0 (sunsetting May 21, 2026, six days from this post) through v25.0. v20.0 is the next oldest, expiring September 24, 2026. If your code is pinned to v19 or earlier, you’re about to break.

Facebook API Pricing, in Plain English

Saying “Facebook has an API” is like saying “Adobe has a product.” There are four developer products on this stack, and the pricing model differs for each.

The Graph API is the foundation. Reading and writing Page data, user profile data, post comments, and reactions all go through it. Free. The bill is rate-limit math and App Review.

The Marketing API sits on top of the Graph API for everything ads-related. Creating campaigns, editing ad sets, pulling Insights, managing custom audiences. Also free. The bill here is the access tier you qualify for and the ad-account quota that comes with it.

The Pages API is the subset of the Graph API that handles publishing to Facebook Pages. It uses Page Access Tokens, the BUC rate-limit formula, and the same App Review flow. Posting to a Page you own is pages_manage_posts. Posting to a Page owned by someone else is the same permission plus Advanced Access.

WhatsApp Cloud API is the outlier. Meta charges per template message delivered. The rules:

• Only template messages are charged. Non-template messages (text, image, document, and similar) are free, but they can only be sent inside an open customer service window.
• A customer service window is a 24-hour window that opens when a WhatsApp user messages your business. Inside that window, non-template messages are free, and Utility templates are also free. Authentication and Marketing templates still follow per-category pricing, with the only override being a Free Entry Point window.
• Outside the customer service window, you can only send template messages, and they’re charged based on category and country.
• A Free Entry Point window opens for 72 hours when a user first messages you from a Click-to-WhatsApp ad or a Facebook Page call-to-action button. During that 72 hours, every message you send is free, including templates.

Template categories are Marketing, Utility, and Authentication. Each category is priced separately. Utility templates are free inside an open customer service window and charged outside it. Authentication templates are charged per delivered message, including inside the customer service window, with the only exception being the 72-hour Free Entry Point window. Marketing templates are charged on delivery in all cases except inside that same Free Entry Point window, where every message is free. Volume tiers unlock lower rates for Utility and Authentication once your monthly volume crosses certain thresholds, aggregated at the business portfolio level across all your WhatsApp Business Accounts.

Per-message rates vary by recipient country. To put rough numbers on the abstraction: in the United States, an Authentication template runs about $0.004 per delivered message and a Marketing template runs about $0.025. India sits at the low end at roughly a cent per Marketing message. Germany sits at the high end above ten cents. Utility rates land between Authentication and Marketing in every country. The current rate card lives on Meta’s WhatsApp pricing page, with downloadable CSVs for USD and other major currencies, and Meta only updates rates on the first day of each quarter with at least one month of advance notice. Always pull the live CSV before plugging numbers into a forecast.

For the Marketing API, there are no per-call costs but there is a rate-limit budget. Each call costs points, with reads at 1 point and writes at 3 points. Limited Access (the default tier) gets heavy rate limiting per ad account, which Meta itself documents as “only for development, not for production apps used by real advertisers.” Full Access gets light rate limiting. Both tiers can manage an unlimited number of ad accounts. To upgrade to Full Access, your app needs 500+ successful Marketing API calls in the trailing 15 days and an error rate below 15% over the last 500 calls.

The Marketing API itself is free, but the ad spend it controls is not. A team running $5,000/month in Meta Ads pays $5,000/month plus zero API fees. The Conversions API (CAPI) for server-side event tracking is also free at the API layer, though you’ll pay infrastructure costs for whatever hosts your event pipeline. Most teams running CAPI through Google Tag Manager Server-Side or a serverless function land between $20 and $200/month in compute, depending on event volume.

The Real Cost: Meta App Review

The free APIs come with an audit you didn’t quote in the project plan.

A new Meta app starts in Development Mode. People with a developer, tester, or admin role on the app can call any permission you’ve added. Strangers cannot. To take a product to real users on Pages, Login, or Marketing, you need Advanced Access on each permission you use, and that’s an App Review submission. WhatsApp Cloud API is the partial exception: a Direct Developer using the API against their own WhatsApp Business Account stays on Standard Access and skips App Review entirely. Building a tool that connects other businesses to their own WhatsApp accounts puts you back in the App Review queue for whatsapp_business_messaging and whatsapp_business_management.

Meta wants to see:

• A screencast that walks through every permission your app uses, end to end
• A public privacy policy URL
• A public terms-of-service URL
• Business verification with a utility bill, tax document, or equivalent
• A test environment reviewers can log into to verify the screencast matches reality
• Data Use Checkup completion every 12 months after approval

A clean submission lands somewhere between five business days and three weeks. A submission with one ambiguous permission or a screencast that skips a step lands in rejection-and-resubmit, which adds another full review cycle. The Reddit thread at r/webdev is a December 2024 walkthrough of how rough the process feels in practice, and the same complaints still show up in newer support threads.

I’d be a bad founder if I didn’t say this part out loud: most small teams underestimate App Review by a factor of three. Two weeks of planned work turns into six weeks of calendar time because the screencast had a missing frame.

The Rate Limit That Surprises People

The Graph API and Pages API throttle by Business Use Case rather than flat per-second limits. For Pages, the formula on Meta’s rate-limiting docs is:

Calls within 24 hours = 4800 × Number of Engaged Users

Engaged Users are the people who clicked, reacted, commented, or shared content on the Page in the prior 24 hours. A Page with 1,000 engaged users yesterday gets a 4.8 million call budget today. A Page with five gets 24,000.

The implication for any product connecting multiple small-business Pages is real. Polling does not scale. Webhooks do. If your architecture assumes flat per-hour limits, the first dozen low-engagement Pages you onboard will hit error code 32 (user or app token) or 80001 (Page or System User token) before lunch.

WhatsApp Cloud has a separate messaging-tier system tied to your business quality rating, applied at the business portfolio level rather than per phone number. New, unverified portfolios start at 250 unique customers per 24 hours. Completing business verification or solution-provider verification through a BSP unlocks the next tier. The ladder then climbs through 10,000, 100,000, and finally unlimited, with Meta evaluating upgrades roughly every 6 hours and bumping you a level if your last seven days hit at least half of your current limit each day while quality stays high.

Tokens Don’t Behave the Way You Expect

User and Page access tokens have a quirk worth knowing before you ship.

Default user access tokens are short-lived. Meta’s long-lived token docs say they expire “in hours.” A short-lived token isn’t useful for any backend product, so the standard pattern is exchanging it for a long-lived token, which lasts about 60 days. Meta only refreshes that long-lived token on days where the user actually makes a request to Facebook’s servers through your app. If your product is a pure backend service and the user never opens it, the token isn’t refreshed, hits 60 days, and the user has to log in again to issue a new one.

Here’s the part that catches people. A Page Access Token issued from a long-lived user access token does not expire. Meta’s docs on Pages access tokens describe this directly. If your app gets a long-lived user token, exchanges it for a Page token, and the user has a role on the Page, that Page token is permanent unless the user revokes app permissions, changes their password, or loses their role.

This is the design assumption for any backend that needs to keep posting to a Page indefinitely. The bug I see most often in support threads is a team handling the 60-day user token refresh correctly but forgetting that Page tokens issued from the original short-lived user token will also expire in hours.

Patterns That Trip Up Most Developers

A few things outside pricing burn real time on this stack.

There is no firehose, only subscriptions. Meta does not stream Page activity. Near-real-time updates require webhook subscriptions at the app level plus a separate subscription per Page you connect. Forget the per-Page step and your dashboard shows yesterday’s data.

Page tokens and user tokens are not the same thing. A user token can post to a Page only after you exchange it for a Page token. The exchange is one extra Graph call. Skipping it is the single most common bug in the support inbox.

Different Meta products live on the same domain with different rules. Graph API, Marketing API, and WhatsApp Cloud API all hit graph.facebook.com, but they account rate limits separately and authenticate with different tokens. Junior developers lose two days to this before realizing it.

Versions deprecate on a 2-year clock. Meta releases 3 to 4 major Graph API versions per year, and each version stays active for roughly two years from its release. v18.0 and earlier are already deprecated. v19.0 sunsets on May 21, 2026. v20.0 expires September 24, 2026. v25.0 is the latest, shipped February 18, 2026.

Real-World Access Examples

The Solo Founder Posting to Their Own Page

Building a side project that auto-publishes daily updates to your Facebook Page.

• Create a Meta app at developers.facebook.com: free
• Add Facebook Login and Pages products: free
• Request pages_manage_posts and pages_read_engagement with App Review for Advanced Access: 1 to 2 weeks for a solo dev
• Exchange a short-lived user token for a long-lived user token, then for a Page Access Token: free
• Total cost: $0, ~2 weeks calendar time

Standard Access alone covers you if the Page is one you administer. Advanced Access only becomes mandatory when your app touches Pages owned by anyone else.

The Agency Running 30 Client Pages

Running a social agency that posts to 30 client Facebook Pages.

• App Review for Advanced Access on pages_manage_posts: 2 to 6 weeks, expect at least one rejection
• Business verification: 1 to 2 weeks running in parallel
• Screencast production, privacy policy, terms-of-service pages: 1 to 2 weeks of dev time
• Each client completes Facebook Login and grants your app a role on their Page
• Generate one long-lived Page Access Token per client (non-expiring if issued from a long-lived user token)
• Total cost: $0 in API fees, 4 to 8 weeks to launch, recurring engineering to keep 30 OAuth handshakes healthy and rate limits respected

The E-Commerce Store Running WhatsApp Support

Running a US-based store that handles customer support and order updates over WhatsApp.

• WhatsApp Cloud API setup plus business verification: 2 to 4 weeks
• Customer-initiated conversations open a 24-hour customer service window where text replies, image responses, and utility templates are free
• Order confirmations sent as utility templates inside that window: free
• Order updates sent as utility templates outside that window: charged at Meta’s per-message US utility rate
• Promotional broadcasts sent as marketing templates: charged on delivery, with the only exception being messages sent inside a 72-hour Free Entry Point window
• Total cost: zero on inbound replies and in-window utility messages, plus the running per-message bill for marketing broadcasts and out-of-window utility updates

Architecting your WhatsApp flow to start from a Click-to-WhatsApp ad gives you a 72-hour Free Entry Point window where every message is free. Most production customer-service flows on WhatsApp are designed around this rule for exactly that reason. For current per-message rates in your country, the official rate cards are at developers.facebook.com/docs/whatsapp/pricing.

The Honest Pitch: Skip the Approval Cycle and Use Blotato

For anyone whose Facebook integration needs to publish posts and nothing more, the calendar cost of doing it yourself is the most expensive part of the project. Blotato handled the Meta App Review once, on our side. You connect your Page, pull an API key from settings, and post with a single HTTP call:

curl -X POST https://backend.blotato.com/v2/posts \
  -H "blotato-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "post": {
      "accountId": "YOUR_FACEBOOK_PAGE_ID",
      "target": { "targetType": "facebook" },
      "content": {
        "text": "Posted to Facebook via the Blotato API."
      }
    }
  }'

One API. Every social platform.

No screencast, no business verification, no Facebook Login OAuth wiring on your end. Swap facebook for instagram, linkedin, x, tiktok, or any of the nine supported targets and the request shape stays the same. The API is included on every paid Blotato plan starting at $29/month. The 7-day free trial covers all features except API access, so you’ll need to upgrade to a paid plan once you’re ready to wire it into your code. The docs live at help.blotato.com/api/start.

There is also an MCP path. Blotato runs an MCP server at https://mcp.blotato.com/mcp, which means Claude Code, Claude Desktop, or any MCP-compatible agent can publish to your Page through a tool call rather than a custom auth flow. If your AI agent decides what to post, the agent can ship it without you writing a single line of OAuth glue. The same logic carries over to Instagram, where I cover the trade-off in Instagram API Pricing.

Start a free week of Blotato.

Blotato is not the answer for every Facebook use case. If your product needs to manage paid campaigns, pull Ads Insights, or run WhatsApp customer support, you’ll go direct to Meta because that’s where those products live. For organic posting and cross-platform automation, the math almost always favors a wrapper.

Sabrina’s Take

I’m biased, obviously. But I built Blotato because the cost of “free” APIs on Meta has always been measured in weeks, not dollars. A solo founder shipping to their own Page is fine on the official route. The moment you need to publish on behalf of customers, App Review becomes the gating constraint on every launch. We did that work once so our users don’t have to keep doing it.

FAQs

Is there a free Facebook API tier in 2026?

Three of Meta’s four developer products are free at the API level. Graph API, Marketing API, and Pages API charge zero dollars per call. WhatsApp Cloud API charges per template message delivered, with non-template messages free inside an open customer service window. The non-monetary costs across all four are App Review or permission review for production apps that touch other people’s accounts, business verification, and the rate-limit budget tied to engaged users or ad-account quota. WhatsApp Cloud API is the partial exception: a Direct Developer using the API against their own WhatsApp Business Account skips App Review and stays on Standard Access.

How does WhatsApp Cloud API pricing work in 2026?

Meta moved WhatsApp Cloud API to per-message pricing on July 1, 2025. Only template messages are charged. Non-template messages (text, image, document) are free as long as they’re sent inside an open 24-hour customer service window, which opens when a WhatsApp user messages your business. Utility templates are free inside that window and charged outside it. Authentication templates are charged per delivered message in nearly every case. Marketing templates are also charged on delivery. The one exception that flips all three to free is the 72-hour Free Entry Point window, which opens when a user first messages you from a Click-to-WhatsApp ad or a Facebook Page call-to-action button. Current per-country rates live at developers.facebook.com/docs/whatsapp/pricing.

How do I get access to the Facebook API?

Register a Meta app at developers.facebook.com, add the products your project needs (Login, Pages, Marketing, WhatsApp), and request the specific permissions your code calls. Standard Access (Limited Access on the Marketing API) activates automatically for accounts with a role on the app. Advanced Access (Full Access on the Marketing API) requires App Review, business verification, and a screencast that demonstrates each permission in your live product.

Why does the Facebook API rate-limit small Pages harder?

The Pages API uses a Business Use Case formula of 4,800 calls per 24 hours multiplied by the engaged users on that Page in the same window. A Page with low engagement gets a small budget. The mitigations are spacing out calls, switching from polling to webhooks, and avoiding bulk operations against Pages with few engaged users.

How long do Facebook access tokens last?

Default user access tokens expire within hours. Long-lived user access tokens, generated by exchanging a short-lived token, last about 60 days. Meta refreshes them once per day on days the user makes a request to Facebook through your app. If your product is a server-only backend that the user never re-engages with, the token will not auto-refresh and the user has to log in again at the 60-day mark. Page Access Tokens issued from a long-lived user token do not expire under normal conditions, which makes them the right choice for backend services that need to keep posting indefinitely. They only invalidate if the user revokes app permissions, changes their password, or loses their role on the Page.

Do Facebook Page Access Tokens really never expire?

Yes, with conditions. When a Page Access Token is generated from a long-lived user access token by a user who has a role on the Page, Meta returns a token with no expiration date. The Graph API Access Token Debugger displays “Expires: Never” for these tokens. They stop working only in specific cases: the user revokes your app’s permissions, the user changes their Facebook password, the user loses their role on the Page, or Meta retroactively invalidates the token for a policy reason. For most backend services posting to Pages, a single long-lived Page Access Token per Page connection is the correct architecture.