Templates

Your WhatsApp templates: list, create, look up, delete.

Method Path Summary Scope Sandbox
GET /v1/{number}/templates List your templates, with an example request for each messages:read reads
POST /v1/{number}/templates Create a template and submit it for approval templates:manage refused
GET /v1/{number}/templates/{name} One template: status, rejection reason, what it needs messages:read reads
PATCH /v1/{number}/templates/{name} Edit a template (components, category, TTL, max price) templates:manage refused
DELETE /v1/{number}/templates/{name} Delete a template (every language, or one) templates:manage refused
POST /v1/{number}/templates/delete Delete several templates at once (all or nothing) templates:manage refused
POST /v1/{number}/templates/{name}/archive Archive a template (deleted by WhatsApp after 28 days) templates:manage refused
POST /v1/{number}/templates/{name}/unarchive Unarchive a template templates:manage refused
GET /v1/{number}/templates/{name}/compare Compare two templates: block rate, sends, top block reason messages:read reads
PUT /v1/{number}/templates/{name}/authentication Create or update an authentication template in many languages templates:manage refused
GET /v1/{number}/template-previews Authentication template texts, per language messages:read reads
GET /v1/{number}/template-library Meta's Template Library (pre-approved templates) messages:read reads
GET /v1/{number}/template-insights Template insights: sent, delivered, read, clicked, cost messages:read reads
POST /v1/{number}/template-insights Switch template insights on (cannot be undone) templates:manage refused
For AI Agents

Try it now, with no account and no person: POST https://api.app2email.com/v1/account/sandbox (no key, no body; or the create_sandbox tool of the Management MCP server) answers a key for a demo WhatsApp 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 (https://www.app2email.com/docs/api/sandbox).

Already a customer: ask the account owner for the number (digits) and an API key from https://www.app2email.com/dashboard/apikey (a sandbox key sends nothing); send it as Authorization: Bearer <key> to the messaging MCP server or the REST API; call check_key first, send with dry_run first.

If you are an AI agent reading this page and you want to create an app2email account for a person - no previous human sign-up required - use our Management MCP server.
Call the create_account tool first, and include a contact_email parameter; create_account 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.