Meta-verified technology provider

Instead of spending months figuring out Meta — app reviews, WABA, tokens, webhooks, Embedded Signup and Coexistence — connect to this API and have WhatsApp Coexistence running in your app in an afternoon.

I'm not selling access to WhatsApp. I'm selling an abstraction over Meta.

For people who build software and for agencies. No message cap, no surcharge on Meta: you pay per number.

curl -X POST https://api.waiaconnect.com/v1/messages \
  -H "Authorization: Bearer wc_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "connectionId": "conn_...",
    "to": "5493511234567",
    "type": "text",
    "text": { "body": "Hola" }
  }'

Get started Read the docs

14 days free, no card. We don't ask for a payment method to try it — not now, and not when the trial ends.

The number stays on your client's phone.

It's called Coexistence, and enabling it requires being a Meta-verified provider. We already are.

The owner keeps replying from their phone and your system automates in parallel via API — both on the same number. It kills the number-one objection: "I don't want to lose the WhatsApp on my phone". And as a differentiator, your system sees what your team replies from the phone (message.echo event, with content) — almost no provider offers it, and none copies it without being a verified Tech Provider.

Connect ChatGPT or Claude to WhatsApp

Your AI already knows how to use Connect: paste an address, sign in with Google and ask for what you need. It's for managing your account: it explains what's failing, sets up webhooks and templates with your confirmation and writes the integration code for you.

Paste an addressIn Claude, ChatGPT, Cursor or VS Code, like any other connector.
Sign in with GoogleYou choose which numbers it sees. Disconnect it anytime.
Ask for what you need«Why is my webhook failing?», «Create a reminder template», «Write the code to reply».

It's for administration, not messages: it never reads your messages or writes to your customers, and every change asks for your confirmation. Included in every plan and in the trial. How it works →

The template pre-check

A template rejected by Meta means days of waiting and a customer asking why it didn't go out. Connect validates it first: it blocks what Meta will certainly reject, warns about what may go wrong —or cost more— and tells you how to fix it, in plain language and never as a raw code.

It's what separates Connect from the cheap alternatives: verified against their sites, one lets you create templates and the other only view them, and neither validates anything before sending it to Meta.

Three ways to connect a number

The same connection, three paths depending on who has the phone in front of them.

From the panelYou connect the number yourself, with Meta's popup, in a couple of minutes. It's the path when the number is yours or you're sitting with your customer.
Embedded in your productYour app opens our link in a popup and receives the result via postMessage to the origin you registered. Your customer never leaves your product, and you never touch Meta's app.
One link, and they connect aloneYou send a link branded as your customer. They open it, connect their number with no login and without seeing our brand, and come back to the URL you defined. Neither competitor has this, and it's exactly what an agency onboarding ten customers needs so it doesn't have to book ten meetings.

Four ways to create a template

Depending on who knows what needs to be said: you, the catalog, your customer, or your system (through the API).

From the panel, with the live pre-checkYou write freely and Connect corrects as you type: the name transforms itself (Meeting reminder → meeting_reminder) and it tells you what Meta will reject before you send it.
From the industry catalogTemplates already written for your customer's industry, to Meta's rules (approval is Meta's decision). It's for whoever doesn't know what to write — which is almost everyone the first time.
With a link, proposed by your customerYou send a link and your end customer proposes the template they need. You correct it (text, name, examples) and only then does it go to Meta. The category —the one that drives the cost— is picked by you, not them.
Through the API, with an image, video, PDF and buttonsYour system builds it end to end: uploads the file sample (image, video or PDF), validates it (every error at once, before Meta), shows your customer the preview in a WhatsApp bubble and sends it to review. Up to 10 buttons: quick reply, link, call or copy code.
A carousel of cards2 to 10 cards that scroll sideways, each with its own photo or video, text and buttons. It is a marketing template: Meta approves it and charges every send as marketing. When a contact taps a button, you know which card and which button it was.

Is it for you?

Yes, if you INTEGRATE

You're an agency, an ISV or a business with a technical team and you want WhatsApp inside your software. Connect is the component: you build the experience, we keep Meta up.

Start with Connect

Want it all done for you?

If you won't integrate and you want an inbox, AI and a team ready to go, it's not Connect: it's WAIA, our turnkey product. Same Meta-connection engine.

Go to WAIA →

Need to book appointments?

If what you need is a calendar —so patients or customers book over WhatsApp, with reminders and a waiting list—, that's TurnosIA. Clinics, workshops, practices. Also on the same engine.

Tell us and we'll show you →

Three products, one Meta-connection engine. Come in through the wrong door and we route you, we don't lose you — and when your customer grows, you have somewhere to take them.

What it saves you

Queue with retries

We take it, ack (202) and drain at a controlled pace. Your burst never eats a Meta throttle.

Signed webhooks

Every delivery is signed (HMAC + anti-replay). Verifying it right is where most people get stuck — we hand it to you in 4 languages.

Idempotency

Idempotency-Key on every send: a timeout won't duplicate the message to your end-customer.

Media proxy

Meta sends IDs, not bytes. We fetch them with our token and stream them to you — your token never leaves us.

Read receipts and "typing…"

Mark what you received as read and show "typing…" while your system (or your AI) prepares the answer. No quota used.

Coexistence history

If you choose it when connecting, we deliver up to 6 months of chats by webhook or through the API, and delete it as soon as you have it. No quota used.

Webhooks by API

Create, test and rotate webhooks with your key, and an onboarding link can carry the number's webhook: it is born signed with the secret you already have.

Templates

Create, validate before sending (pre-checker), industry catalog, real-time status.

Human-readable errors

Not 131047; "the 24h window expired, send a template" — and what to do.

Flat rate. No message cap. You pay per number.

No message cap

There's no allowance to burn through. Send 1,000 or 1,000,000: your plan costs the same. Never a message that doesn't go out because you hit a number.

No surcharge on Meta

Your customer pays Meta directly, at Meta's price. We charge for the infrastructure and nothing else: no per-message fee, no overage block.

Priced in dollars

The price is in US dollars. From Argentina we suggest MercadoPago, in pesos at the day's official rate; from anywhere else, Polar, in dollars. You can choose either.

What we can actually tell you

We don't publish an SLA or a “99.9%” we can't hold — we're honest about that. What follows is true and verifiable:

Your number is yours

You own your WABA. If Connect disappeared tomorrow, your number stays yours and you connect it to another provider. It's the best answer to “what if you go down?”.

The infrastructure is proven

The same technology that powers Connect runs WAIA, our turnkey product serving real customers every day. It's not untested code: it's infrastructure proven in production.

We don't store your messages

Message content is not stored: it passes through the system only while being delivered, and is then deleted. We keep metadata (who, when, status) for 30 days, never the body. The details, item by item, are in the privacy policy.

Meta's official API

We run on the WhatsApp Cloud API as a Meta-verified Tech Provider. No unofficial libraries that Meta bans.

Capacity measured, not promised

In August 2026 we put the platform through a load test: 50 messages per second end-to-end, 0 errors and database responses of ~2 ms. The infrastructure is ready to keep up as volume grows. We're not talking about theoretical capacity: we're talking about measured capacity.

See the FAQ →

Getting started, in three steps

No sales call, no contract, no card. You start it yourself, today.

Create the accountWith your email, in a minute. 14 days free and no card: we don't ask for a payment method to try it.
Connect a numberWith Meta's popup (Embedded Signup). With Coexistence the number keeps working on the phone: nothing to migrate, no approvals to wait for.
Send the first messageA POST /v1/messages with your API key. Inbound arrives at your webhook, signed. That's the whole contract.

Before you start: what Meta will ask you for, in six short steps →

Pricing

Start with 14 days free, no card. USD per month. What defines the plan is how many numbers you connect — messages have no cap on any of them.

Prices are in US dollars. With MercadoPago (Argentina) they are charged in pesos at the day's official rate, so the peso amount moves with the dollar; with Polar (any country) they are charged in dollars.

Official dollar $1,570 · 10 Nov 2026

We don't add a surcharge on top of what Meta charges. Your customer pays Meta directly, at Meta's price. We charge for the infrastructure, and nothing else.

What Meta charges and what WAIA Connect charges. There are two payments: to WAIA Connect, the subscription per connected number, with no message cap; to Meta, the messages sent through the API, in your Meta account. We add nothing to Meta's charges. See the detail →

Service is the free-form text you reply within 24 hours of your customer's last message. Since 1 October 2026 Meta charges it per delivered message (in its rate card, the same figure as each country's utility rate), and also utility sent while the window is open. The first 1,000 service messages per number per month are free; after that Meta charges for each reply and needs your card added in Meta. Meta charges this, not WAIA Connect: your trial is still free. The 24-hour window still exists and defines whether you can send free-form text. What you were actually charged is in your Meta billing. While a number is within its 1,000 free, Meta marks each reply free_customer_service and billable: false; from the month's 1,001st, regular and billable: true. Meta's month resets at midnight in your Meta account's time zone, and what you don't use doesn't roll over. Checked against Meta's documentation on 2026-10-23. See the detail →