Messages sent and received, newest first

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

Messages sent from the number (direction out, with their status and times) and received from contacts (direction in). Filters: a time window, the direction, the status of sent messages, one contact, or one broadcast. Page with next_cursor.

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)

    Only messages at or after this time. ISO 8601, eg 2026-10-25T10:00:00Z.

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

    Only messages before this time. ISO 8601.

    e.g. 2026-10-26T00:00:00Z
  • direction string

    in: received. out: sent. Left out: both.

    inout
  • status string

    Sent messages only: queued, accepted, sent, delivered, read or failed. Not with direction=in.

    queuedacceptedsentdeliveredreadfailed
  • to string

    Only with this contact (full number, digits, with country code).

    e.g. 61412345678
  • broadcast string

    Only the messages of this broadcast (its code).

    e.g. k3XbQ9rTzP2mWv7a1c9e
  • limit integer 1–200 default 50

    How many (1 to 200, default 50).

  • cursor string

    The next_cursor of the previous answer, unchanged. Leave out for the first page.

Responses

200 The messages.
Fields
  • success boolean
  • request_id string
  • messages object[]
    17 item fields
    • direction string
      inout
    • message_id string
      e.g. wamid.HBgLNjE0MTIzNDU2NzgVAgARGBJTQU1QTEVfVEVTVF9FVkVOVAA=
    • to string

      direction out.

      e.g. 61412345678
    • from string

      direction in: the contact's number, or their business-scoped user id when no number is known.

      e.g. 61412345678
    • from_user_id string

      direction in: the contact's business-scoped user id, when WhatsApp sent one.

    • media_url string

      direction in, media messages: app2email's stored copy (GET /media/{message_id}, with your key). WhatsApp's own media ids expire after 7 days.

    • name string

      direction in: the contact's name.

    • status string

      direction out.

      queuedacceptedsentdeliveredreadfaileddeletedunknown
    • sent_by string
    • text string
    • media string
    • time string (date-time)
    • times object

      direction out.

      7 fields
    • error object

      direction out, when it failed.

      1 fields
    • reply object

      direction out: the contact's reply.

  • next_cursor string

    Pass it as cursor for the next page. Left out on the last page.

  • count integer

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.
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.