API
WhatsApp Webhooks on WAPing
Subscribe to HTTPS endpoints for inbound and delivery-related events from your QR-linked WhatsApp session. Exact event names and payloads are documented on docs.waping.app—this page summarizes behavior and limits.
Webhooks are part of WAPing’s developer surface: you register an HTTPS URL in the dashboard, verify ownership when prompted, and receive POSTs when messages or session events occur. Payload shape and event catalog are maintained on docs.waping.app—do not assume Meta Cloud API webhook formats.
- Access: Webhook configuration requires a tier that includes developer features (Starter+). Free tier does not include API keys or outbound webhooks.
- Model: Events are emitted from your linked WhatsApp session (QR), not from Meta’s BSP-hosted Cloud API pipeline.
- Reliability: Expect retries on transient failures; implement idempotent handlers and return 2xx only after you persist the event.
Also see: Pricing and API access, webhook integrations hub, and WAPing vs Twilio WhatsApp for model context.
Product UI: Automation & flows · Technical reference: Webhooks (overview).