WhatsApp Business API in Mexico: Meta cost and options

According to the WhatsApp Business Platform's official pricing page (developers.facebook.com, read on October 27, 2026), Meta has charged per message since July 1, 2025, only for business-to-user messages that were delivered. Messages from the user to the business are not charged. The categories are marketing, utility and authentication (all by template) and service (a reply inside the 24-hour window).

For Mexico, the page says MXN billing started on January 1, 2026 and that marketing rates increase on October 1, 2026. Each currency has its own files: list rates (CSV), volume tiers for utility and authentication (CSV) and a combined PDF. The MXN values do not appear in the page text but in those files, so check the current table on the day you decide.

The same page says each business phone number has an allowance of 1,000 delivered service messages per month, with no rollover, and that charging starts at message 1,001 from October 1, 2026. A payment method must be on file, or service sending stops after the allowance. How much you pay depends on the template category.

The practical rule: outside the 24-hour window after the customer's last message, only an approved template works. Inside the window, the conversation is a service conversation. Understand the mechanics in WhatsApp Business API: costs and paths.

1) Download the MXN rate file from Meta's pricing page and note the rate for each category you will use. 2) Estimate monthly messages in each category: how many campaigns (marketing), how many order or appointment notices (utility), how many access codes (authentication) and how many replies beyond the allowance (service). 3) Multiply volume by rate. 4) Add the cost of the partner or platform you use, if any, and your team's time.

The site's API cost calculator uses the official rates in Brazilian reais (BRL), with the check date. For Mexico, use it as a reasoning template and swap in the values from the MXN table. The site does not publish the peso rates here because they were not read from an official file at the time of writing.

Many companies combine them: official for notifications that need the badge and scale, and unofficial for day to day conversation. See the honest comparison in the unofficial API, an honest guide and in ZapZap vs the official API.

ZapZap is an unofficial API: it connects the number by QR code to a WhatsApp Web session and exposes sending and webhooks through an API, with no per-message charge. The price is R$15 per active number per month, in Brazilian reais, prepaid; see the pricing page for terms and check at checkout which payment method is available for your country, because the site does not promise local currency.

The number goes with country code 52 and digits only. Because the format of Mexican mobile numbers has caused confusion historically, use the check endpoint before sending: it returns whether the number is registered and the correct identifier. This applies to any country.

curl -X POST https://api.zapzapapi.com/api/v1/SEU_INSTANCE_ID/chat/check \
  -H "Content-Type: application/json" \
  -H "x-api-key: SUA_API_KEY" \
  -H "x-api-secret: SEU_API_SECRET" \
  -d '{"numbers":["525512345678"]}'

curl -X POST https://api.zapzapapi.com/api/v1/SEU_INSTANCE_ID/send/text \
  -H "Content-Type: application/json" \
  -H "x-api-key: SUA_API_KEY" \
  -H "x-api-secret: SEU_API_SECRET" \
  -d '{"number":"525512345678","text":"Hola, tu cita quedó confirmada."}'

Unofficial use violates WhatsApp's Terms and the number can be restricted; no tool removes that. The usual factors lower the risk: contacts who know you, consent, varied text, intervals and warm-up. See anti-ban and the risk matrix.

On data, Mexico has a federal law on the protection of personal data held by private parties, built around the privacy notice to the person and consent. The rule was updated recently, so confirm the current text with a local lawyer. This guide is not legal advice. For the same discussion in Brazil, see data protection for WhatsApp (LGPD).

In Mexico, WhatsApp is an everyday channel for talking to shops, clinics, schools and service providers, and many people prefer to settle everything by message instead of calling. Mexican Spanish uses "celular" and "mensaje" and, in a commercial tone, usually addresses the customer as "tú" or "usted" depending on the sector. The country code is 52 and mobile numbers have 10 digits.

Local companies charge in Mexican pesos (MXN) and many issue a tax invoice (factura), which weighs on the choice of vendor: ask your accountant how to handle the invoice for a service bought from abroad, since ZapZap bills in reais. For a non-Mexican company serving Mexican customers, use local Spanish, not machine-translated Spanish, in messages.

Appointment confirmation: "Hola, [Nombre]. Te confirmamos tu cita el [día] a las [hora] en [lugar]. Si necesitas cambiarla, respóndenos por aquí." Order follow-up: "Hola, [Nombre]. Tu pedido [número] ya salió y llega entre [hora] y [hora]. Cualquier duda, aquí estamos."

Always include a clear exit in campaigns, such as "Si ya no quieres recibir mensajes, responde BAJA", and handle the request in your database. Business-initiated messages outside the 24-hour window require a template on the official API; on the unofficial one, the rule is about behavior, not templates, and the restriction risk remains.

If the number is critical, if compliance is required or if notification volume is high, the official API is the choice most aligned with the Terms. If you need flexible conversation, want to test fast and accept the restriction risk, the unofficial one works as an entry point. Many businesses use both.

In any case, start small: a secondary number, contacts who know you and a few weeks of measuring replies before investing in business verification and templates.