Submit-Info

Forms a business defines as a plain list of questions. app2email turns each one into a WhatsApp form and a web page; what people send becomes a submission that moves through stages in a shared inbox and sets off automations: replies, e-mails, calculations and calls to outside systems. Start with GET /submit/guide, build everything with one POST /submit/setup, then publish the form.

Method Path Summary Scope Sandbox
GET /v1/{number}/submit/guide The Submit-Info guide for agents: every key, rule and example submissions:manage reads
GET /v1/{number}/submit/settings Submit-Info settings: the switch, the config and the public code submissions:manage reads
PUT /v1/{number}/submit/settings Switch Submit-Info on or off and change its settings submissions:manage refused
POST /v1/{number}/submit/setup Apply or dry-run a whole setup: forms, lists, automations submissions:manage refused
GET /v1/{number}/submit/presets The ready-made setups (presets), or one complete preset submissions:manage reads
GET /v1/{number}/submit/forms The forms of the number submissions:manage reads
POST /v1/{number}/submit/forms Create a form from a definition or a preset submissions:manage refused
GET /v1/{number}/submit/forms/{key} One form: definition, fields, links and WhatsApp state submissions:manage reads
PUT /v1/{number}/submit/forms/{key} Change a form: name, on or off, archive, definition submissions:manage refused
DELETE /v1/{number}/submit/forms/{key} Delete a form (archived when it has submissions) submissions:manage refused
POST /v1/{number}/submit/forms/{key}/publish Publish a form to WhatsApp submissions:manage refused
POST /v1/{number}/submit/forms/{key}/send Send a form to a contact, with values filled in submissions:manage refused
GET /v1/{number}/submit/lists The choice lists (sites, jobs, price lists) submissions:manage reads
PUT /v1/{number}/submit/lists/{key} Create a list or replace its items submissions:manage refused
DELETE /v1/{number}/submit/lists/{key} Delete a list submissions:manage refused
GET /v1/{number}/submit/submissions The submissions, filtered and paged (JSON or CSV) submissions:manage reads
POST /v1/{number}/submit/submissions Create a submission from data you already hold submissions:manage refused
GET /v1/{number}/submit/submissions/{id} One submission with files, activity and what can be done submissions:manage reads
PATCH /v1/{number}/submit/submissions/{id} Change a submission: stage, assignee, tags, answers submissions:manage refused
DELETE /v1/{number}/submit/submissions/{id} Delete a submission, or erase it for good submissions:manage refused
POST /v1/{number}/submit/submissions/{id}/notes Write an internal note on a submission submissions:manage refused
POST /v1/{number}/submit/submissions/{id}/reply Message the submitter, with up to 3 buttons submissions:manage refused
POST /v1/{number}/submit/submissions/{id}/files Attach a file to a submission submissions:manage refused
POST /v1/{number}/submit/submissions/{id}/run Run a manual automation on a submission submissions:manage refused
GET /v1/{number}/submit/members The team: who works in the shared inbox submissions:manage reads
POST /v1/{number}/submit/members Invite a person to the shared inbox by e-mail submissions:manage refused
PUT /v1/{number}/submit/members/{id} Change a member's role, abilities or forms submissions:manage refused
DELETE /v1/{number}/submit/members/{id} Remove a member from the inbox submissions:manage refused
GET /v1/{number}/submit/automations The automations submissions:manage reads
POST /v1/{number}/submit/automations Create an automation: when, if, do submissions:manage refused
POST /v1/{number}/submit/automations/try Try an automation on a real submission, saving and sending nothing submissions:manage real change
GET /v1/{number}/submit/automations/{id} One automation submissions:manage reads
PUT /v1/{number}/submit/automations/{id} Change an automation, or switch it on or off submissions:manage refused
DELETE /v1/{number}/submit/automations/{id} Delete an automation submissions:manage refused
GET /v1/{number}/submit/runs The automation run log, step by step submissions:manage reads
GET /v1/{number}/submit/connections The connections to outside systems submissions:manage reads
PUT /v1/{number}/submit/connections/{key} Create or change a connection (HTTP, OpenAPI or MCP) submissions:manage refused
DELETE /v1/{number}/submit/connections/{key} Delete a connection submissions:manage refused
POST /v1/{number}/submit/connections/{key}/test Test a connection: can app2email reach it and sign in? submissions:manage real change
POST /v1/{number}/submit/connections/{key}/refresh Read a connection's operations or tools again submissions:manage refused
GET /v1/{number}/submit/connections/{key}/functions What an action can call on a connection submissions:manage reads
GET /v1/{number}/submit/report Submission counts by form, stage, day and assignee submissions:manage reads
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.