Submission counts by form, stage, day and assignee

GET https://api.app2email.com/v1/{number}/submit/report
scope: submissions:manage sandbox: reads MCP: get_submit_report

Scope: submissions:manage. The submissions made in the last days days (1 to 365, default 30) counted by form, by stage, by day (in the business time zone) and by assignee, with how many are open now and the average hours from submission to a closed stage. 400 invalid_range when days is not 1 to 365.

Path

  • number string required pattern ^[0-9]{8,15}$

    Your app2email WhatsApp number - the number the message is sent FROM. Full number with country code, digits only.

    e.g. 4976659348270

Query

  • days integer 1–365 default 30

    How many days back, 1 to 365. Default 30.

Responses

200 The report.
Fields
  • success boolean
  • request_id string
  • days integer

    The range that was counted: submissions created in the last so many days.

  • timezone string

    The time zone by_day is cut in.

  • open_now integer

    Submissions in an open stage now.

  • closed_avg_hours number | null

    Average hours from submission to a done or cancelled stage, of those closed in the range. null: none was closed.

  • by_form object[]

    Per form, most first: how many, and how many of them are still open.

    4 item fields
  • by_stage object[]

    Per form and stage key.

    4 item fields
  • by_day object[]

    Per day of creation.

    2 item fields
    • day string
      e.g. 2026-11-13
    • count integer
  • by_assignee object[]

    Per member; id 0 = not assigned.

    4 item fields

Errors

  • 400 The request is malformed (missing or invalid fields, query parameters or times).
  • 401 Missing, invalid, revoked or expired API key.
  • 403 The key is valid but this call is not allowed: the key lacks the scope the call needs (insufficient_scope), the address is not allowed for the key (ip_not_allowed), the number or plan does not allow it, a recipient opted out or is not opted in, or a problem with the WhatsApp account.
  • 404 The number, template, message, broadcast, webhook, delivery, opt-in, logged request, booking or Flow was not found.
  • 429 A monthly plan limit, the number's own monthly cap, the key's daily cap, a WhatsApp rate limit, the API rate limit (rate_limited), or the webhook test limit (too_many_tests) was reached. Retry-After and error.retry_after_seconds say how long to wait.
  • 500 Unexpected error on app2email's side.
  • 503 app2email's connection to the WhatsApp account needs attention, or the request log is not available right now.
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.