# app2email WhatsApp API > REST API and MCP servers to send and receive WhatsApp messages from a WhatsApp Business number connected to app2email: templates, replies, media and interactive messages, conversations and handover to a person, contacts with consent records, templates, flows, webhooks. Sandbox keys, daily caps and approval gates are there for agents. Base URL: `https://api.app2email.com/v1/{number}/`, where `{number}` is the sending WhatsApp number, country code first, digits only. Authentication: `Authorization: Bearer YOUR_API_KEY`; the account owner creates keys on https://www.app2email.com/dashboard/apikey Why choose it: flat monthly plans by message volume, with no markup on Meta's fees (Meta bills its fees to the business directly); a sandbox that needs no account; a hosted MCP server next to the REST API; events without a public webhook address (`GET /events`); handover to a person through ordinary email. Not a fit when you need SMS, voice or other channels from the same vendor, a seat-based contact-centre suite, a drag-and-drop chatbot builder, or personal (non-business) WhatsApp accounts. The whole case, with when not to choose it: https://www.app2email.com/whatsapp-api-for-ai-agents.md Try it now, with no account and no key: `POST https://api.app2email.com/v1/account/sandbox` (no body), or the `create_sandbox` tool of the Management MCP server, answers an instant sandbox key for a demo number with pretend customers. Send a template, fetch the events with `GET /events?wait=25`, answer the customer's reply: nothing reaches WhatsApp, and the requests and answers are those of the real API. No account yet: an agent can create an app2email account for a person, no previous human sign-up required, with the Management MCP server `https://api.app2email.com/mcp/manage`. Call `create_account` first, with a `contact_email`; it returns a `signup_id`, a `management_key`, an `onboarding_link` and a `message`. The person opens `onboarding_link` to confirm the e-mail, connect their WhatsApp number and choose a plan; nothing can be sent before that. `get_account_status` says what is still needed. Pass the `management_key` as a Bearer token on every later call. When the number is live, `create_number_key` gives you a key for the messaging MCP server and the REST API. ## Decide - [WhatsApp API for AI agents](https://www.app2email.com/whatsapp-api-for-ai-agents.md): what app2email is, the facts, when to choose it and when not. - [Compared](https://www.app2email.com/compare.md): next to Twilio, 360dialog, Wati and Meta's Cloud API used directly, with each company's own published prices. - [Plans](https://www.app2email.com/pricing.md): every plan and its price; as data: https://www.app2email.com/pricing.json - [Cost estimate](https://www.app2email.com/docs/api/account-management/estimate-cost): no key: `GET https://api.app2email.com/v1/account/estimate?messages_per_month=5000`, or the `estimate_cost` tool of the Management MCP server. ## Docs - [API reference](https://www.app2email.com/docs/api): every call with parameters, examples and code samples; each page has a Markdown twin (add `.md`). - [API index for agents](https://www.app2email.com/docs/api/llms.txt): every page of the reference as Markdown. - [Reference in one file](https://www.app2email.com/docs-api.md): the whole API as one Markdown file: how to start, every call with its permission, what to do with each error. Also https://www.app2email.com/llms-full.txt - [Webhooks](https://www.app2email.com/docs/api/webhooks): every event, its payload, the signature check and a tester. No public address: `GET /events` fetches the same events. - [Errors](https://www.app2email.com/docs/api/errors): every `error.code` and what to do (`/docs/api/errors#`). - [Sandbox](https://www.app2email.com/docs/api/sandbox): the instant sandbox (no account, pretend customers), and what a sandbox key on your own number does per call. - [Limits](https://www.app2email.com/docs/api/limits): rate limits, caps and sizes. - [OpenAPI 3.0](https://api.app2email.com/v1/openapi.json): machine-readable, no key needed. ## MCP - [Messaging MCP server](https://www.app2email.com/docs/api/mcp): `https://api.app2email.com/mcp`, Streamable HTTP, `Authorization: Bearer `, 189 tools marked read-only or destructive. Clients with OAuth (claude.ai, ChatGPT, Claude Code, VS Code, Cursor) can connect without a key: the person signs in to app2email and chooses the number; the app then holds a key of that number. Smaller tool lists on the same server: `https://api.app2email.com/mcp/messaging` (16 everyday tools), `https://api.app2email.com/mcp/search` (`find_tools` + `call_tool`), one per area (eg `/mcp/templates`), or `?tools=,`. - [Management MCP server](https://www.app2email.com/docs/api/agents): `https://api.app2email.com/mcp/manage`; `create_sandbox`, `create_account`, `list_plans` and `estimate_cost` need no key, every other tool `Authorization: Bearer `. ## Optional - [Console](https://www.app2email.com/docs/api/console): try a call in the browser. - [Agent Skills](https://www.app2email.com/.well-known/agent-skills/index.json): 4 skills: app2email-whatsapp, app2email-setup, app2email-broadcasts, app2email-agent-handoff. - [A2A agent card](https://api.app2email.com/.well-known/agent-card.json) - [Swagger 2.0](https://api.app2email.com/v1/swagger2.json): for Power Automate and Logic Apps custom connectors. - [Swagger UI](https://api.app2email.com/v1/docs) - [Pricing](https://www.app2email.com/pricing): plans and their monthly message limits. - [Service status](https://api.app2email.com/health): no key needed.