app2email API Pricing

Setup

The whole setup of an integration (Book-and-Pay, Submit-Info, Order-and-Pay with its catalog and pictures, Tickets-and-Pay with its events) as ONE file of JSON Lines: download it, change it, check it, apply it, undo it. Made for AI agents and scripts: every problem names its line.

Method Path Summary Scope Sandbox
GET /v1/{number}/setup/guide How setup files work: types, rules, examples bookings:manage|orders:manage|tickets:manage|submissions:manage reads
GET /v1/{number}/setup/export Download the setup as a file bookings:manage|orders:manage|tickets:manage|submissions:manage reads
POST /v1/{number}/setup/check Check a setup file (changes nothing) bookings:manage|orders:manage|tickets:manage|submissions:manage reads
POST /v1/{number}/setup/apply Apply a setup file bookings:manage|orders:manage|tickets:manage|submissions:manage refused
POST /v1/{number}/setup/assets Upload a picture for a setup file bookings:manage|orders:manage|tickets:manage|submissions:manage refused
GET /v1/{number}/setup/jobs Setup checks, applies and undos bookings:manage|orders:manage|tickets:manage|submissions:manage reads
GET /v1/{number}/setup/jobs/{id} One setup job bookings:manage|orders:manage|tickets:manage|submissions:manage reads
POST /v1/{number}/setup/jobs/{id}/undo Undo an applied setup file bookings:manage|orders:manage|tickets:manage|submissions: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.