WhatsApp Business API in Colombia: Meta cost and options

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

For Colombia, the page says COP billing started on April 1, 2026 and that utility and authentication rates increased on October 1, 2025. No Colombia-specific change is listed for October 1, 2026 in the page text. The peso values are not on the page but in the rate files per currency (list CSV, volume-tier CSV and combined PDF). Download the current table on the day you decide.

According to the same page, each business phone number has 1,000 delivered service messages per month in its allowance, with no carry-over to the next month, and charging applies from message 1,001 since October 1, 2026. A payment method must be on file so that service sending is not interrupted after the allowance.

Outside the 24-hour window after the customer's last message, only an approved template works. The full mechanics are in WhatsApp Business API: costs and paths.

1) Download the COP rate file from Meta's pricing page and note the rate for each category. 2) Estimate monthly volume per category: campaigns (marketing), order or appointment notices (utility), codes (authentication) and replies beyond the allowance (service). 3) Multiply volume by rate. 4) Add the platform or partner cost and your team's hours.

The API cost calculator uses the official rates in Brazilian reais (BRL) with the check date; use it as a template and swap in the COP values. We do not publish peso rates here because they were not read from an official file at the time of writing.

Combining both worlds is common. To decide, read the unofficial API, an honest guide and the comparison ZapZap vs the official API.

ZapZap is an unofficial API with no per-message charge: the number is connected by QR code and you send and receive through the API and webhooks. The price is R$15 per active number per month, in Brazilian reais, prepaid; see the pricing page and checkout for which payment methods are available for your country, since the site does not promise local currency.

The number goes with country code 57 and digits only, with the 10-digit mobile number. Use the check endpoint before sending to confirm it is registered and to get the correct identifier.

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":["573001234567"]}'

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":"573001234567","text":"Hola, tu cita quedó confirmada."}'

Unofficial use violates WhatsApp's Terms and the number can be restricted. The factors that lower risk are the same in any country: contacts who know you, authorization, varied text, intervals and warm-up. See anti-ban and the risk matrix.

In Colombia, personal data processing follows Law 1581 of 2012, which requires prior authorization from the data subject and a processing policy, with the Superintendency of Industry and Commerce as the authority. Confirm the requirements for your case with a local lawyer. This guide is not legal advice. For the comparison with Brazil, see data protection for WhatsApp (LGPD).

In Colombia, WhatsApp is a regular channel for customer service and sales, from small shops to clinics and real estate agencies. The country code is 57 and mobile numbers have 10 digits, starting with 3. Colombian Spanish tends to be formal and courteous, with plenty of "usted" in customer service, and the currency is the Colombian peso (COP).

Anyone selling into the country should think about the end customer's payment method and their own invoicing: local companies usually expect invoices in pesos and local payment methods. ZapZap charges in reais, and the available methods appear at checkout; confirm there before counting on a specific method.

Appointment confirmation: "Buenos días, [Nombre]. Le confirmamos su cita el [día] a las [hora] en [lugar]. Si necesita cambiarla, responda a este mensaje." Order follow-up: "Hola, [Nombre]. Su pedido [número] ya va en camino y llega entre [hora] y [hora]. Con gusto le ayudamos con cualquier duda."

In campaigns, include the exit: "Si no desea recibir más mensajes, responda RETIRAR", and record the request. Remember that Law 1581 of 2012 asks for prior authorization from the data subject. On the official API, business-initiated messages outside the 24-hour window require an approved template; on the unofficial one, risk depends on your sending behavior and remains.

If the number is the heart of the business and losing it is unacceptable, or if your Colombian customer requires a certified channel, the official API is the safest choice with respect to the Terms. If you need flexible conversation, want to test quickly 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. Only then decide whether it is worth investing in business verification and official templates.

Who is responsible for the data and the authorizations? Which will be the main WhatsApp number and which the spare? How much volume of each message category do you expect per month? Who will handle replies and during what hours? Who tracks connection status? If any of them has no answer, the operation is not ready to scale.