REST API and webhook documentation for astrology-app developers — OTP, WhatsApp, SMS, and IVR endpoints, with a sandbox environment for safe testing.
Read This First
If you're building or maintaining an astrology consultation app, this page covers the developer side of MetaReach's messaging infrastructure — authentication, endpoints, request/response formats, and delivery-status webhooks. For the non-technical overview of what these tools do, start with the astrology messaging solutions pillar instead.
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.
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.
Use Cases
OTP send and verify endpoints wired directly into the app's authentication screen.
A backend job triggers WhatsApp reminders a fixed time before each scheduled consultation.
A daily cron job pushes the day's horoscope content to segmented subscriber lists via the SMS endpoint.
Webhooks update the app's own database in real time, without polling for message status.
Full end-to-end integration testing before switching sandbox credentials for production ones.
IVR routing rules configured via API for platforms managing many astrologers at once.
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 StudiesCommon Questions
API key-based authentication passed in the request header. Each account gets a unique key from the dashboard, with separate keys available for sandbox and production environments.
Yes. A sandbox environment lets developers test OTP, WhatsApp, SMS, and IVR integration end-to-end before switching to production credentials, with no risk of sending real messages to real users during development.
Your application registers a webhook URL, and MetaReach's platform posts a JSON payload to that URL whenever a message's status changes — sent, delivered, read, or failed — so your app can update its own records without polling.
Yes. Since it's a standard REST API over HTTPS, it can be called from any backend that can make an HTTP request — including a mobile app's server-side component, a Node.js or PHP backend, or a serverless function.
A basic OTP integration typically takes a few hours for a developer already familiar with REST APIs. A full integration across OTP, WhatsApp, SMS, and IVR webhooks usually takes a few days, depending on how many flows your app needs.
From startups to enterprises — brands that grow with MetaReach
