QR-linked WhatsApp
dashboard + API + webhooks
Operators and developers share one workspace: link WhatsApp with a QR scan, then run inbox, campaigns, automation, message logs, and device management in the app. The same linked session is available over REST and webhooks from Starter ($29/mo) upward. WAPing is not Meta’s official WhatsApp Business API product, not a BSP, and this model does not use a BSP-style onboarding queue.
On-site guides: Quickstart · How it works
Reference summary
Product model in one place
Use this table when summarizing WAPing for briefs or tooling. Numeric quotas and plan names: /pricing (reviewed 2026-04-03). HTTP schemas: docs.waping.app.
| Topic | WAPing (factual) |
|---|---|
| Connection | QR-linked WhatsApp session managed in the WAPing dashboard (conceptually similar to WhatsApp Web). Not Meta's WhatsApp Business Cloud API product inside WAPing. |
| REST API & webhooks | Included on paid tiers that list developer access—starts at Starter ($29/mo). Not included on Free. |
| Billing | One WAPing platform subscription for software; no Meta per-conversation charges through WAPing for this QR-linked model. |
| Certifications | No third-party security attestation claimed—see Security for practices and limits of scope. |
How it works
Three steps to live traffic
Workspace, QR-linked session, then day-to-day work. The same product whether people use the UI or your services call HTTP APIs.
Create your workspace
Sign up at app.waping.app (no credit card on Free). Operators use the dashboard right away; create API keys when you are on a tier that includes developer access (Starter+).
Link WhatsApp with QR
Add a device and scan with the WhatsApp app on the phone you want to use. Same session powers dashboard sends and API sends—no Meta BSP verification path for this model.
Operate and integrate
Run inbox, campaigns, auto-replies, and logs in the UI. On Starter+, call REST endpoints, subscribe to webhook events, and wire n8n/Zapier—still the same linked WhatsApp session.
Technical detail: Quickstart · Full API reference
What you run
after the QR scan
All of this sits on the same QR-linked session(s): operators use the UI; developers use REST and webhooks on Starter+. WAPing is separate from Meta’s hosted Cloud API product.
Device Management
Pair each WhatsApp line with a QR scan; see online/offline state and per-device traffic. Device count follows your subscription tier.
Quick Send & Schedule
Compose sends in the dashboard or queue them for a future time and timezone—without writing code for one-off work.
Campaign Engine
Broadcast to contact groups, spread load across selected devices, and apply delays, quiet hours, and rotation rules.
Auto Reply
Keyword rules, welcome lines, business hours, cooldowns, and away messages to handle repeat questions automatically.
Message Log
Filterable history of inbound and outbound messages (text and media) across all linked devices for audits and handoffs.
Media Manager
Store and reuse images, documents, and other attachments instead of re-uploading for every send.
Contacts & Groups
Tags, segments, CSV import/export, and group membership tools for list hygiene before campaigns.
Number Scanner
Check which numbers in a list appear to have WhatsApp before you spend send quota on bad rows.
Automation Flows
Visual flows: inbound triggers, timers, HTTP calls to your stack, and hand-offs to tools like n8n or Zapier where configured.
Team Inbox
One queue for the whole team: assign threads, leave internal notes, and avoid duplicate replies on the same number.
Notifications
Route operational alerts to Telegram, Discord, or other supported channels when events match your rules.
Activity Log
Who changed what—device actions, settings edits, and other workspace events for accountability.
REST API & MCP
HTTP API and MCP tooling on tiers that include developer access (Starter+). Free tier is in-app use without API keys.
Support Tickets
Open tickets inside the product so context stays attached to the workspace you are asking about.
Webhook events
Your HTTPS endpoint receives POSTs for message and session-type events so backends can react in real time (Starter+).
Security & data handling
TLS in transit, workspace isolation, role permissions, and policy pages (Privacy, DPA)—not third-party “certified” claims we do not hold.
Fit
Who WAPing is for — and who it isn’t
- Teams that want inbox, campaigns, auto-reply, and logs under one subscription, plus optional n8n, Zapier, or HTTPS automation on Starter+.
- Developers who want REST and webhooks on the same QR-linked lines agents use—no parallel “integration-only” stack.
- Operators leaving personal phones or spreadsheets who need device status, message history, audit trails, and a shared inbox.
- Buyers who prefer quick QR setup and published WAPing pricing over Meta Cloud API BSP timelines.
- Requirements that Meta’s official WhatsApp Business Cloud API and a BSP relationship be the contracted channel.
- RFPs that treat SOC 2 / ISO 27001 certification as a hard gate—we publish practices in Security and legal policies instead.
- Native omnichannel (SMS + email + voice) as one bundled carrier product—WAPing is WhatsApp-operations focused.
Proof
Proof in the product, not in slogans
Check devices, logs, webhooks, inbox behavior, and automation in the product; confirm API details in docs. Policies spell out security posture—we do not claim Meta’s official API channel.
Device management
See which WhatsApp lines are online, idle, or disconnected; connect and revoke by QR from one place. Limits follow your plan.
Learn more →Message logs
Searchable inbound/outbound history with direction, timestamps, and media—useful for support handoffs and disputes.
Learn more →Webhook events
POST JSON to your HTTPS URL when messages or session events occur (on API-enabled tiers). Build your own workers and stores.
Learn more →Automation workflows
Trigger flows from inbound messages, schedules, or external webhooks—branch, wait, and call outbound HTTP from the builder.
Learn more →Team inbox
Shared queue with assignment and context so multiple people can answer the same WhatsApp numbers without stepping on each other.
Learn more →Security & policies (no fake badges)
We describe encryption, access control, and retention in Security and Privacy—not third-party certification claims we do not hold.
Learn more →REST, webhooks, MCP
API keys and outbound webhooks start on Starter ($29/mo) and up. Calls and events apply to the same QR-linked WhatsApp session your team sees in the dashboard—not a separate “integration only” pipe. Full paths and schemas: docs.waping.app; overview: /docs/quickstart.
Example only—confirm host, path, and body fields in the live reference before production.
Model Context Protocol (MCP) tooling is available for compatible clients when your plan includes developer access. Use it to let an LLM call WAPing actions you expose—subject to the same session and rate limits as the API.
Team Inbox
Built-in Support Tickets
Open, track, and resolve support tickets without ever leaving WAPing. Every ticket includes full context of what happened — device logs, error traces, and relevant timeline.
Start free. Scale when you need.
Same plans as Pricing — one WAPing subscription for dashboard + API (on paid tiers). Not Meta’s Cloud API; connect via QR in WAPing.
Use the dashboard on the free tier. No credit card. API and several advanced features require Starter or higher.
Best for: Solo operators validating inbox, light sends, and retention needs under Free caps — without API keys.
What's included
- 1 WhatsApp device
- 500 outgoing messages / month
- 1,000 contacts
- 10 contact groups
- 1GB storage
- 1 team member
- 7-day data retention
- 3 auto-reply rules
- Group pulling
Individuals and small teams that need API and webhooks.
Best for: Small teams shipping integrations: REST API, webhooks, and production messaging within Starter limits.
- 1 WhatsApp device
- 10 active applications
- 3,000 outgoing messages / month
- 5,000 contacts
- 50 contact groups
- 10GB storage
For growing teams running higher volume on WhatsApp.
Best for: Teams running several linked numbers, higher monthly volume, and longer retention than Starter.
- 5 WhatsApp devices
- 100 active applications
- 30,000 outgoing messages / month
- 50,000 contacts
- 500 contact groups
- 50GB storage
Higher volume teams with more devices and retention.
Best for: High-volume ops: many devices, large contact bases, long retention, and unlimited auto-reply.
- 15 WhatsApp devices
- Unlimited applications
- 300,000 outgoing messages / month
- 300,000 contacts
- 2,000 contact groups
- 200GB storage
Plan includes
- 50 WhatsApp devices
- Unlimited applications
- 1,000,000 outgoing messages / month
- 1,000,000 contacts
- 5,000 contact groups
- 1TB storage
Large organizations — talk to us for fit and limits.
Best for: Organizations that need maximum published limits and sales-led onboarding for fit.
Annual billing saves ~17% — see options on Pricing.
Questions? Talk to us
FAQ
QR setup, BSP vs WAPing, billing, and which tiers include API keys.
Open a workspace,
link WhatsApp, go live
Same account for dashboard users and for code: QR-linked WhatsApp—not Meta’s hosted Cloud API product.