Whose is the number and the WABA?

Yours. You connect through Meta's Embedded Signup, the token lives sealed on our side and you can disconnect at any time from the console.

Who pays for the messages?

Meta bills conversations directly to your WABA. We never mark up a message; we charge per connected number, monthly.

What are the rate limits?

Six hundred calls per minute per account, and a sending budget of a thousand per hour and five thousand per day, on top of Meta's own limits per number. Every 429 carries Retry-After.

Can I send free-form messages anytime?

Only inside the 24-hour window after the customer's last message, which is Meta's rule. Outside it, send an approved template.

Does it work with n8n?

Yes: an HTTP Request node with the bearer key for sending, a Webhook node for receiving. The docs have the recipe, and the MCP Client node also works.

Do I pay before connecting a number?

Yes: the subscription starts with one number and it is what opens the console. Once you subscribe you connect the number through Meta's Embedded Signup, and the bill follows how many you keep connected.

OfficialWhatsApp through Meta's API

We connect your system to official WhatsApp

One REST API and one MCP server over your own WhatsApp Business numbers: send any message type, manage templates and flows, and receive every event on your webhook, signed. Built for n8n, CRMs and agents.

Create a developer account Read the docs

From R$ 39.90 per month, per number.

Webhook deliveries

message.received200
message.status200
template.status502
number.update200

POST https://your-system.com/webhook

X-Zaiped-Signature: t=1757160000000,v1=9f2c…

Three steps to the first message

We keep the Meta side out of your way: the account, the numbers and the webhooks are yours, and we hold the plumbing.

1
Connect a number
Sign in to the console and connect your WhatsApp Business number through Meta's Embedded Signup. It stays in your name and your WABA.
2
Create an API key
One key per environment. We show the secret once and store only its hash.
3
Call the API or the MCP
List your numbers, send a message, register a webhook. The same key works for the REST API and the MCP server.

Everything the Cloud API does, one call away

We expose what we already run for thousands of conversations: the same code, behind a key instead of a session.

Messages
Text, media, location, contacts, reactions, interactive buttons and lists, CTA URLs, carousels, flows, products and templates. Mark as read with a typing indicator.
POST /v1/messages
Templates
Create, submit, edit, unpause and delete message templates, with Meta's status mirrored back to you.
POST /v1/templates
Flows
Create WhatsApp Flows from JSON, push, publish, deprecate and read the responses your customers submit.
POST /v1/flows
Numbers
Business profile, conversational components, QR codes with prefilled messages and voice calling settings, live from Meta.
GET /v1/numbers
Media
Upload once and send from any number; download what your customers send you through a signed URL.
POST /v1/media
Analytics
Sent, delivered, read, failed and received per day, billing categories and the top errors for any period.
GET /v1/analytics

Webhooks you can trust

Every event that reaches us from Meta reaches your endpoint, signed and retried.

message.receivedA customer sent a message to one of your numbers, with the media id when there is one.
message.statusA message you sent was delivered, read or failed, with Meta's error and pricing data.
template.statusMeta approved, rejected or paused a template.
number.updateQuality rating, messaging limit or display name of a number changed.
account.noticeA WABA-level notice: restriction, violation, lost access.
call.eventA voice call event or status change.

HMAC signature in the header

We send X-Zaiped-Signature with a timestamp and an HMAC-SHA256 over the raw body. Verify it with the secret we show once, and retry safely: each delivery carries its own id.

POST https://seu-sistema.com/webhook
X-Zaiped-Event: message.received
X-Zaiped-Delivery: YOUR_DELIVERY_ID
X-Zaiped-Signature: t=1757160000000,v1=HMAC_SHA256

{
  "id": "YOUR_DELIVERY_ID",
  "event": "message.received",
  "createdAt": 1757160000000,
  "data": { "from": "+5511999999999", "type": "text", "text": "Oi" }
}

An MCP server, remote and ready

Point Claude, Cursor or the n8n MCP node at one URL with your API key. Every route is a tool, with the same validation and the same errors as the REST API.

Example configuration

{
  "mcpServers": {
    "zaiped": {
      "url": "https://zaiped.com/mcp",
      "headers": { "Authorization": "Bearer zp_..." }
    }
  }
}

Tools mirror the API: list_numbers, send_message, create_template, list_flows, create_webhook and the rest.

One price per connected number

No setup fee and no fee per message: Meta bills the conversations directly to you. We charge for the numbers you keep connected, and the price drops as you grow.

How many numbers?

10numbers

Tier	Qty.	Per number	Subtotal
1 to 9 numbers	9	R$39.90	R$359.10
10 to 49 numbers	1	R$29.90	R$29.90
50+ numbers	0	R$19.90	R$0.00

Monthly total

R$389.00/ month

Average of R$38.90 per number

You save R$10.00 (3%) per month

Every plan includes

Unlimited API calls (within Meta's limits)
Configurable, signed webhooks
Remote MCP server
Coexistence with the WhatsApp Business app
Support over WhatsApp
No setup or activation fee

Subscribe

No setup fee · Cancel anytime

Questions developers ask

The short answers. The docs have the long ones.

We connect your system to official WhatsApp

Three steps to the first message

Connect a number

Create an API key

Call the API or the MCP

Everything the Cloud API does, one call away

Messages

Templates

Flows

Numbers

Media

Analytics