60%
0
Days
0
Hours
0
Minutes
0
Seconds
btn
WhatsApp API & Messaging Gateway · Case Study

Rapiwa — a developer-first WhatsApp API gateway that ships messages at scale

How SpaGreen Creative built a production-grade WhatsApp API gateway with 99.9% uptime, sub-second delivery and an SDK so clean that integration is a 20-minute task instead of a two-week project.

  • 99.9%Uptime since launch
  • <1sMedian message delivery
  • 8 moConcept to production

Trusted by 8,200+ businesses across 110+ countries · NDA on request · Reply in under 24h

IndustryMessaging, CRM & automation
RegionGlobal
Timeline8 months end-to-end
EngagementProduct build (in-house product)
PlatformsREST API · Webhooks · Dashboards
Core stackNode.js · Express · MongoDB · Docker · AWS
Cloud Solutions IT Consulting Technology Strategy Business Solutions Analytics & Reporting Cloud Solutions IT Consulting Technology Strategy Business Solutions Analytics & Reporting
Cloud Solutions IT Consulting Technology Strategy Business Solutions Analytics & Reporting Cloud Solutions IT Consulting Technology Strategy Business Solutions Analytics & Reporting
The challenge

WhatsApp APIs are easy to demo and hard to run in production

Anyone can wire up a WhatsApp message in a Postman tab. Running messaging at scale is a different problem entirely: rate limits, queue back-pressure, retry policies, message templating, media uploads, webhook reliability, multi-number routing, opt-out compliance, and a thousand small edge cases that only show up when traffic is real. Most WhatsApp libraries on the market handle the demo and explode at the scale.

Rapiwa was built to remove that gap. Developer ergonomics first — clean REST, predictable JSON, idempotent sends, signed webhooks — with a queue-driven core that absorbs spikes instead of buckling under them.

Our approach

Queue-driven from day one, observable from day two

We chose Node.js + Express for the API surface and MongoDB for the message ledger. Every send is enqueued, idempotent on a client-supplied request ID, and processed by a pool of workers that respect WhatsApp Cloud API rate limits per phone number. Failures fall into a dead-letter queue with structured retries; webhook deliveries are signed so customers can verify origin without a shared secret over the wire.

Observability was non-optional. Every message moves through a state machine (queued → sent → delivered → read → failed) with structured logs at each step, so support questions like “why didn’t my customer get this message” have a one-query answer.

Engagement details

Our Solution

Cooperation Model

Rapiwa WhatsApp API is a developer-friendly product built in-house by SpaGreen Creative, enabling businesses to send, receive and automate WhatsApp messages securely at scale.

Team

1× UI/UX Designer2× Backend Engineers (Node)1× Frontend Engineer (React)1× QA Engineer1× DevOps Specialist1× Product Manager

Methodology

Agile with API-first design: every endpoint shipped with OpenAPI docs, contract tests and a working SDK sample before the feature was considered done.

Tools

FigmaNode.js · ExpressMongoDBDocker · KubernetesGitHub ActionsTrelloPostman

Technologies

Node.js + ExpressMongoDB (message ledger)RabbitMQ / BullMQ queuesRESTful APIs & signed webhooksWebSockets (live inbox)ReactJS (dashboards)Meta WhatsApp Cloud API

Timeframe

8 months — from initial planning and prototyping to full deployment, observability hardening and live scalability testing.

Operational metrics

How Rapiwa performs under real traffic

Production telemetry aggregated across customer accounts during peak send windows.

99.9%API uptimeMeasured externally over 12 months
<1sMedian deliveryFrom API accept to recipient delivered receipt
8M+Messages per monthSustained across customer base, scales linearly
0Lost messagesIdempotent send + dead-letter queue + signed webhooks
Outcomes & constraints

Results

Key Achievements

  • Launched a developer-first WhatsApp API gateway with clean REST + SDK
  • Sub-second median delivery sustained at 8M+ messages/month
  • Achieved 99.9% uptime measured by external probes
  • Integrated Meta WhatsApp Cloud API with full compliance and templating
  • Built signed webhooks & idempotent sends for zero-loss messaging

Challenges

  • Sustaining API speed during burst sends without violating rate limits
  • Ensuring data privacy and WhatsApp Cloud API policy compliance
  • Building an architecture that scales across dev / staging / production cleanly
  • Making integration feel like 20 minutes, not two weeks, for new developers

We migrated off a competitor that promised 99% uptime and delivered 96. Rapiwa has done 99.9 since the day we cut over. The dashboards alone saved us a customer-support hire.

CTOB2B SaaS Vendor · Verified customer, under NDA
4.9/5
Building on WhatsApp?

Ship a Rapiwa-grade WhatsApp messaging gateway.

Talk to a senior messaging engineer. We’ll review your volume, templates and integration plan and send a fixed-price proposal in 24 hours.

  • Idempotent send + signed webhooks
  • Queue-driven, sub-second delivery
  • Meta Cloud API compliant
  • Dashboards & observability built-in

Trusted by 8,200+ businesses · 110+ countries · NDA on request · Free quote in 24h

Buyer FAQ — running WhatsApp messaging at scale

Rapiwa is a developer-first gateway on top of the Meta WhatsApp Cloud API. It adds idempotent sends, signed webhooks, structured retries, a message ledger, dashboards and rate-limit-aware queueing — the production glue most teams build themselves and regret later.

A white-label Rapiwa deployment with your branding, billing and account isolation takes 4 to 8 weeks. A fully custom messaging gateway with multi-channel support (WhatsApp + SMS + email + push) takes 12 to 20 weeks.

Rapiwa sustains 8M+ messages per month across its current customer base with sub-second median delivery. The architecture scales linearly — adding worker pods adds throughput without changing the data model.

Yes. Rapiwa uses the official Meta WhatsApp Cloud API, respects per-number rate limits, enforces template approvals before send, honours opt-out and quality-rating signals, and includes audit logs for compliance reviews.

Yes. Incoming messages, status updates and media downloads all flow through signed webhooks. A live inbox UI is included for support teams to handle conversations without a separate CRM.

Yes — the REST API and signed webhooks are designed for integration. Pre-built connectors are available for Shopify, WooCommerce, HubSpot and Salesforce, with custom integrations available on retainer.

For a custom build, you own 100% of the source code and infrastructure. Customer data is stored on infrastructure under your control (AWS, GCP or your private cloud) — SpaGreen never accesses production data.

White-label Rapiwa starts at $6,500 USD. Custom WhatsApp gateways with multi-tenant SaaS billing, advanced dashboards and CRM integrations start at $14,000 USD and scale based on scope.

Can we help you with a messaging project?

From WhatsApp gateways to multi-channel messaging (WhatsApp + SMS + email + push), partner with SpaGreen Creative to ship a reliable, observable messaging layer your product can depend on.

Contact SpaGreen Creative