REST API
your stack, same linked WhatsApp
Call WAPing from your backend to send messages, query history, and manage workspace objects. One capability: reliable HTTP integration with the same QR-linked devices your team uses in the app—not a parallel Meta Cloud API setup.
Pain point
Dashboard-only ops do not scale
When order systems, CRMs, or custom workers need to trigger WhatsApp messages, copy-pasting from the UI breaks audit trails and slows releases. You need a single contract between your servers and the platform that already holds the linked session.
Why it matters
The API turns WAPing into a component in your architecture: retries, queues, and monitoring live in your code, while delivery still goes out through the same QR-linked device your operators trust.
One clear capability
Server-to-server control of messaging and workspace data with Bearer keys, scoped to your tenant—documented on docs.waping.app, aligned with plan limits on pricing.
How it works
Request lifecycle (conceptual)
- Issue a key on a tier that includes API access (Starter ($29/mo)+). Store it as a secret; never expose it in browsers or mobile apps.
- Target a device — outbound actions specify which linked WhatsApp session (
deviceIdin docs) should send or receive context. - Call HTTPS with
Authorization: Bearerand, for sends, a stable idempotency header so retries stay safe (see Send message guide). - Handle errors — distinguish 401/403 (auth or plan) from session disconnects and 429 throttling (Errors, Rate limits).
Practical examples
- Order worker — your storefront queues a job; the worker POSTs a send for “shipped” updates tied to one support device.
- Nightly sync — a cron job reconciles CRM tags, then updates contact fields via the API before a morning campaign run.
- Support bridge — ticketing webhooks create internal tasks; agents still reply from the team inbox, while status updates go back through the API.
Limitations & caveats
- Not Meta’s Cloud API — no BSP onboarding path inside WAPing for this connection model.
- Outbound volume and device counts follow your plan; HTTP 429 can still apply under burst load.
- Exact paths and JSON fields change with product releases — treat docs.waping.app as source of truth.
Ship the integration
Start on a paid tier with API access, then align your client with the live OpenAPI reference.
Where this fits
REST calls carry sends and workspace operations from your backend. Typical flows: OTP verification flows, order system integration. Technical entry points: API quickstart, Authentication. Plans and API access are on pricing.
FAQ
Straight answers—same facts as our pricing and security pages.