app2email API Pricing

Send this number's webhooks to app2email again

DELETE https://api.app2email.com/v1/{number}/webhook-redirect
scope: webhooks:manage sandbox: refused MCP: remove_webhook_redirect

Removes your URL at Meta. From the next webhook on, app2email receives the number's messages again; messages sent to your URL before stay there.

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

Responses

200 Removed at Meta.
Fields
  • success boolean required
    e.g. true
  • request_id string required
    e.g. k3x9a
  • 8 fields
    • active boolean required

      true: Meta sends this number's webhooks to your URL, not to app2email.

    • url string | null

      Your URL at Meta. null: none.

    • account_url string | null

      An alternate URL set for the whole WhatsApp Business Account (used when the number has none). null: none.

    • mode string required

      off: app2email gets and handles the messages as usual. webhook_redirect: Meta sends them to your URL. pass_through: app2email passes them on to your URL (see pass_through).

      offwebhook_redirectpass_through
    • goes_to string required

      Where Meta sends the number's messages now.

      webhook_redirectaccount_webhookapp2email
    • set_at string (date-time) | null

      When it was set through app2email. null: not known.

    • set_by string | null

      Who set it through app2email: the API key's name or the dashboard user.

    • pass_through object | null

      The Pass-Through Webhook. null: none.

      9 fields
      • active boolean required

        false: switched off after deliveries kept failing (disabled_reason); app2email then handles the messages itself. PUT again to switch it on.

      • url string required
      • secret string required

        Your signing secret: each POST has X-Hub-Signature-256: sha256=<hex HMAC-SHA256(secret, raw body)>, as Meta signs, and X-App2email-Signature.

      • use_in_app2email boolean required

        true: app2email also handles the messages (Inbox, e-mail forwarding, auto replies, agents, apps). false: they only go to your URL.

      • webhook_id string required

        It is one of the number's webhooks (GET /v1/{number}/webhooks: pass_through true): deliveries, retries and redeliver work there.

      • set_at string (date-time) | null
      • set_by string | null
      • disabled_reason string | null
      • last_delivery object | null
        3 fields
  • meaning string
  • warning string

    After a PUT: what stops working on app2email.

Errors

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