--- title: "Zaiped for developers: WhatsApp API and MCP" description: "A REST API and a remote MCP server on top of Meta's official WhatsApp Cloud API: your numbers, messages, templates, flows and signed webhooks. A monthly subscription per connected number, from R$ 39.90." lang: "en-US" canonical: "https://zaiped.com/en/developers" alternate: "https://zaiped.com/developers" --- # 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. From R$ 39.90 per month, per number. ## 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. - **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. - **Create an API key**: One key per environment. We show the secret once and store only its hash. - **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. - **Templates**: Create, submit, edit, unpause and delete message templates, with Meta's status mirrored back to you. - **Flows**: Create WhatsApp Flows from JSON, push, publish, deprecate and read the responses your customers submit. - **Numbers**: Business profile, conversational components, QR codes with prefilled messages and voice calling settings, live from Meta. - **Media**: Upload once and send from any number; download what your customers send you through a signed URL. - **Analytics**: Sent, delivered, read, failed and received per day, billing categories and the top errors for any period. ## Webhooks you can trust Every event that reaches us from Meta reaches your endpoint, signed and retried. - **message.received**: A customer sent a message to one of your numbers, with the media id when there is one. - **message.status**: A message you sent was delivered, read or failed, with Meta's error and pricing data. - **template.status**: Meta approved, rejected or paused a template. - **number.update**: Quality rating, messaging limit or display name of a number changed. - **account.notice**: A WABA-level notice: restriction, violation, lost access. - **call.event**: A 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. ## 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: https://zaiped.com/mcp 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. | Tier | Per number | | --- | --- | | 1 to 9 numbers | R$39.90 | | 10 to 49 numbers | R$29.90 | | 50+ numbers | R$19.90 | ### 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 No setup fee ยท Cancel anytime ## Questions developers ask ### 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. ## Ship the first message today Create the account, connect a number, copy the key. The docs walk you through the rest.