Whether you're building a new astrology consultation app or adding messaging to an existing platform, this overview covers what it actually takes to plan a MetaReach integration for OTP, WhatsApp, SMS, and IVR APIs — the APIs available, authentication and setup, sandbox testing, and a realistic timeline for a working integration.
What You Can Integrate
MetaReach's API integration for astrology platforms uses API key authentication, REST/JSON endpoints for OTP, WhatsApp, SMS, and IVR, and webhook callbacks for real-time delivery status. A sandbox environment is available for end-to-end testing before switching to production credentials. This page is a conceptual overview — for full endpoint references, request/response payloads, and sandbox credentials, contact our developer team directly.
Endpoints
All endpoints accept and return JSON over HTTPS, authenticated via an API key in the request header.
| Method | Endpoint | Purpose |
|---|---|---|
| POST | /v1/otp/send | Send a login/signup OTP to a phone number |
| POST | /v1/otp/verify | Verify a user-submitted OTP code |
| POST | /v1/whatsapp/send | Send a WhatsApp template message (reminder, kundli delivery, etc.) |
| POST | /v1/sms/send | Send a single or bulk SMS (e.g. horoscope batch) |
| GET | /v1/messages/{id}/status | Poll the delivery status of a sent message |
| POST | /v1/webhooks/register | Register a callback URL for real-time delivery status events |
Sample Request — Send OTP
Sample Webhook Payload — Delivery Status
Illustrative example only — actual field names and response formats are provided in full during onboarding.
Authentication & Setup
Sandbox & Testing
A sandbox environment is available before production access, so you can test OTP flows, message templates, and webhook handling without sending real messages to real numbers. Typical integration timeline for a basic OTP + WhatsApp send-and-track setup: 1-2 weeks for a team already familiar with REST APIs.
Common Integration Patterns
App calls OTP API → user enters code → app verifies via MetaReach's verification endpoint.
Booking system triggers a scheduled WhatsApp send via webhook, timed relative to session start.
Scheduled job calls the Bulk SMS API against a segmented subscriber list each morning.
MetaReach webhook fires to your CRM/lead system the instant a missed call registers.
Go Further
The non-technical side of each tool this API powers.
Session reminders, kundli delivery, and follow-up messages on WhatsApp.
Explore WhatsApp for AstrologersDaily horoscope and panchang push notifications at scale.
Explore Horoscope AlertsRoute incoming calls to the right astrologer automatically.
Explore Call RoutingZero-cost missed-call lead capture for individual astrologers.
Explore Missed Call LeadsSee how consultation platforms and astrologers use this infrastructure.
View Case StudiesGeneral API documentation covering the full MetaReach messaging platform.
View API DocsCross-vertical reference — astrology platforms are technically SaaS products too.
View SaaS & ERP Integration GuideCommon Questions
Yes — sandbox access with test credentials is provided during onboarding, before any production sending.
For a team already familiar with REST APIs, a basic OTP + WhatsApp integration typically takes 1-2 weeks. More complex flows (IVR routing, multi-channel orchestration) take longer.
No — sandbox testing doesn't require DLT registration or WhatsApp Business setup. DLT/PE registration applies to SMS (and applicable telecom voice) and is required before production SMS sending; WhatsApp uses a separate WhatsApp Business setup with recipient opt-in and approved templates, required before production WhatsApp sending.
Yes — each API (OTP, WhatsApp, SMS, IVR) can be integrated independently based on what your platform needs.
From startups to enterprises — brands that grow with MetaReach
