WhatsApp cost and volume of this number

GET https://api.app2email.com/v1/{number}/analytics/pricing
scope: messages:read sandbox: reads MCP: get_pricing_analytics

Meta's pricing_analytics for this number: delivered messages and their cost per period. Estimates, not the invoice.

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

  • since string (date-time)

    Start, ISO 8601. Default: 30 days before until. At most 1 year back.

    e.g. 2026-10-01T00:00:00Z
  • until string (date-time)

    End, ISO 8601. Default: now.

    e.g. 2026-11-01T00:00:00Z
  • granularity string default day

    Default day.

    half_hourdaymonth
  • countries string

    Only these countries: comma separated 2-letter codes.

    e.g. DE,AT
  • dimensions string

    Break down by: comma separated category, type, country, tier, phone. Default category,type.

    e.g. category,type,country

Responses

200 The data points.
Fields
  • success boolean required
    e.g. true
  • request_id string required
    e.g. a1n2l
  • since string (date-time)
  • until string (date-time)
  • granularity string
  • currency string
  • data_points object[] required
    9 item fields
    • start string (date-time)
    • end string (date-time)
    • MARKETING, UTILITY, AUTHENTICATION, AUTHENTICATION_INTERNATIONAL, MARKETING_LITE, SERVICE, REFERRAL_CONVERSION.

    • pricing_type string

      REGULAR, FREE_CUSTOMER_SERVICE, FREE_ENTRY_POINT.

    • country string
    • tier string

      Volume tier, eg 0:750000 (with dimensions tier).

    • phone_number string
    • volume integer
    • cost number

      In the WhatsApp Business Account's currency. Not given when the account uses a partner's credit line.

  • totals object
    2 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.
  • 422 The request is understood but cannot be sent (template parameters, media, text, recipient, or a WhatsApp rule such as the 24 hour window).
  • 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.
  • 502 WhatsApp (Meta) returned an error or could not be reached.
  • 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.