WhatsApp October 2026 Pricing: Official API vs. UnifyPort

Take two WhatsApp support numbers, each delivering 10,000 ordinary replies to customers in Brazil in a month. Under the October 2026 rules, their combined Meta Service message charge is $122.40. A UnifyPort workspace with those two messaging accounts has one included messaging account and one paid messaging account, giving a subscription estimate of $10 per month.

Those figures cover different line items: official-channel message delivery and an account subscription. Neither is the full cost of a support operation, and the integration paths offer different capabilities. The useful comparison is which path fits your workflow and which costs grow as traffic increases.

This guide is for teams connecting WhatsApp to an existing CRM, support application, or AI workflow. Prices were checked on September 28, 2026. Meta examples use the USD rate card effective October 1, 2026, with the applicable free allowance deducted.

What changes on October 1?

Meta’s non-template announcement and updated English pricing documentation describe changes to business replies sent through the official WhatsApp Business Platform.

Message or situation	Through September 30, 2026	From October 1, 2026
Incoming customer messages	No Meta message charge	Still no Meta message charge
Service replies from a human or third-party AI within the 24-hour window	No Meta Service charge	First 1,000 delivered Service messages per business number each month are free; subsequent deliveries use the recipient market’s rate
Utility templates delivered within the 24-hour window	No Meta charge for that delivery	Charged under Utility rules; the Service allowance does not apply
Eligible 72-hour free entry point window	Free message delivery	Exception remains; Meta Business Agent token usage is separate

The 24-hour customer service window remains a sending restriction. Once it closes, a qualifying template is needed. An ordinary text reply does not automatically become an approved template.

A free entry point window requires an eligible Click-to-WhatsApp ad or Facebook Page call-to-action entry and a business response within 24 hours. It runs independently of the customer service window. An ordinary inbound inquiry does not automatically create 72 hours of free delivery.

The 1,000-message allowance belongs to each business phone number, resets monthly, and does not roll over. One-to-one and group Service deliveries share it; group messages consume one unit per delivered recipient. All calculations below use one-to-one messages.

Check billing before the change. The August announcement asks businesses to add a payment method by September 30. The English pricing page updated September 10 clarifies that, without one, Service messages within the allowance are still delivered, but delivery stops after the allowance is exhausted. Teams expecting to exceed it should meet the original setup deadline.

Official API costs depend on the number and recipient market

For one business number serving one recipient market, with only ordinary Service replies and no free entry point traffic:

Monthly Meta Service charge
  = max(delivered Service messages − 1,000, 0)
  × the recipient market's Service rate

If a customer sends two messages and the business delivers five replies, those five replies count toward Service usage. An accepted API request is not evidence of delivery or a billable message.

The following rates come from Meta’s October rate card. Both monthly columns cover one business number, after deducting 1,000 free messages. All amounts are USD.

Recipient market	Service rate per message
India	$0.0014
North America	$0.0034
Brazil	$0.0068
Singapore	$0.0160
United Kingdom	$0.0220
Germany	$0.0550

After the free allowance, the monthly estimates for one number are:

Recipient market	10,000 deliveries/month	100,000 deliveries/month
India	$12.60	$138.60
North America	$30.60	$336.60
Brazil	$61.20	$673.20
Singapore	$144.00	$1,584.00
United Kingdom	$198.00	$2,178.00
Germany	$495.00	$5,445.00

These are estimates, not customer bills or measured savings. They assume an unchanged rate throughout the month, no other message categories, and no 72-hour free entry point traffic. They exclude providers, support software, AI, taxes, and currency conversion. Service messages do not receive Utility or Authentication volume-tier discounts.

For a number serving several markets, do not deduct 1,000 messages from each market. Keep delivery order, recipient market, and billing status, then add the applicable rates for deliveries after that number’s shared allowance is exhausted.

UnifyPort subscriptions depend on paid messaging accounts

UnifyPort connects messaging accounts through unofficial interfaces. Its current pricing page uses graduated monthly subscriptions in USD. Each workspace includes one free messaging account, with paid accounts priced separately by band.

Paid messaging account positions	Monthly price per account
1–5	$10.00
6–10	$8.00
11–200	$5.00
201–1,000	$4.50
1,001 onward	$4.00

For ten paid messaging accounts:

5 × $10 + 5 × $8 = $90/month

Together with the included account, this provides an allowance of eleven messaging accounts. Reaching the second band does not reprice all ten paid accounts at $8.

This subscription estimate grows with the account count. The unofficial UnifyPort path is not billed using Meta Cloud API’s Service rate card. Any traffic you continue sending through the official API still needs its own cost calculation.

The estimate covers messaging account subscriptions only. Confirm account eligibility, traffic, throughput requirements, terms, and taxes when arranging service. A fixed subscription is not a promise of unlimited throughput or guaranteed delivery. Paid plans are currently confirmed and activated with the team.

A like-for-like traffic example with two support numbers

Assume two WhatsApp numbers serving only Brazil, each with the same monthly reply volume. Meta’s allowance is deducted separately for each number. The UnifyPort workspace contains only these two accounts: one included and one paid.

Through September 30, 2026, these ordinary Service replies have no Meta Service charge. The table compares the combined monthly charges for both numbers from October. Total replies are twice the first column.

Monthly replies per number	Meta Service from October	UnifyPort subscription estimate
800	$0.00	$10.00/month
10,000	$122.40	$10.00/month
100,000	$1,346.40	$10.00/month

For the middle row:

Meta: 2 × (10,000 − 1,000) × $0.0068 = $122.40
UnifyPort: 1 included account + 1 × $10 = $10.00
Difference between the listed charges: $112.40/month

These are selected cost components under the same one-to-one, no-template, no-free-entry assumptions. The high-volume UnifyPort row illustrates the subscription formula; capacity and applicable terms still require confirmation. Development, operations, support software, AI, staff, and taxes are excluded on both sides. The $112.40 difference is not a demonstrated reduction in total operating cost.

The first row matters: when each number stays within its allowance, Meta’s Service charge remains zero. Avoiding that fee alone is not a reason for a low-volume team to migrate.

Distribution also matters. If all 1,600 replies come from one number and the other sends none, Meta charges 600 × $0.0068 = $4.08. Two allowances cannot be pooled for use by either number.

Compare integration capabilities as well as price

Path	Costs to include	When to evaluate it
Direct official Cloud API	Meta messages plus integration, monitoring, and operations	You require official templates or workflows and can maintain the integration
Official service provider	Meta-related charges plus contractual platform, seat, number, or message fees; avoid double-counting bundled charges	You need a hosted inbox, team management, onboarding, or support
UnifyPort	Messaging account subscriptions plus your application and other services	You need ordinary account access or multiple platforms behind a shared API and webhook workflow

Providers use different commercial models. Do not assume a universal 15% or 20% markup. Separate fixed fees, Meta charges, extra per-message charges, seats, and AI, and check which items a quoted package already includes.

UnifyPort can reduce the separate API and event integrations required across platforms. Its unofficial access is not equivalent to the official Cloud API’s capabilities or authorization. Confirm any dependency on official templates, Meta-native features, or an official integration requirement before comparing price.

Account continuity is part of the decision. Platforms may change access rules, restrict accounts, or suspend access. UnifyPort’s terms describe those boundaries. Include reauthorization, failure handling, and continuity in a trial; monthly pricing does not establish delivery rates or account risk.

AI adds another cost component

Third-party AI replying through the official API generally adds model or agent fees to any billable Meta Service deliveries. Using UnifyPort does not make third-party AI free.

Meta Business Agent has a separate model: its announcement lists $2 per million billable tokens, covering the relevant AI processing and delivery. Do not add another Service-category charge to the same message or apply that token model to every third-party AI system. See Meta’s non-template pricing documentation.

For AI support, measure the replies needed to resolve an issue, the model cost, and any human handoff cost.

Recalculate your own traffic before the deadline

Start with a complete recent month, split by business number, recipient market, delivered message category, and free entry point traffic. Apply October rates, then add your provider, software, and AI costs.

If official capabilities are essential, set up billing and usage monitoring to keep October operations running. If ordinary messaging accounts or cross-platform support are the priority, use UnifyPort’s included account to validate the important flows before adding paid accounts.

Estimate subscriptions on the pricing page, then check the quickstart and WhatsApp connection guide.

Sources and verification date

• Meta non-template pricing announcement, dated August 25, 2026: dates, categories, and Business Agent charging.
• Meta pricing documentation, English update dated September 10, 2026: the newer allowance and payment clarification take precedence in these examples.
• October 1 rate card downloads: USD attachment, Service column, not July Utility rates.
• UnifyPort pricing and terms: subscriptions, estimate scope, and service boundaries.

All sources were checked September 28, 2026. Later changes are subject to the relevant official documentation and agreed order terms.