flow.status_changed

Send this to my URL
Flows X-App2email-Event: flow.status_changed

A flow was published, throttled, blocked or deprecated, Meta raised or cleared an endpoint or client alert, or its Flow JSON version expires soon. WABA-wide: every number gets it.

data

  • flow_id string required
  • change string required

    status (FLOW_STATUS_CHANGE); else Meta's event in lower case: client_error_rate, endpoint_error_rate, endpoint_latency, endpoint_availability, flow_version_expiry_warning (and any event Meta adds); other when Meta sent no event.

  • event string

    Meta's event: FLOW_STATUS_CHANGE, CLIENT_ERROR_RATE, ENDPOINT_ERROR_RATE, ENDPOINT_LATENCY, ENDPOINT_AVAILABILITY, FLOW_VERSION_EXPIRY_WARNING.

  • old_status string

    Left out when the flow was just created.

    DRAFTPUBLISHEDDEPRECATEDBLOCKEDTHROTTLED
  • new_status string
    DRAFTPUBLISHEDDEPRECATEDBLOCKEDTHROTTLED
  • message string

    Meta's text.

  • warning string

    FLOW_VERSION_EXPIRY_WARNING: the Flow JSON version will freeze soon.

  • alert_state string
    ACTIVATEDDEACTIVATED
  • threshold number
  • error_rate number
  • p50_latency integer
  • p90_latency integer
  • availability number
  • errors object[]
    3 item fields
  • timestamp string (date-time)

Inside the envelope {id, type, created, number, test?, data}: envelope, headers, signature.

Caused by

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.