This overview covers what it actually takes to plan a MetaReach integration for OTP verification, WhatsApp, SMS, and IVR APIs into a matrimony platform — the APIs available, authentication and setup, sandbox testing, and a realistic timeline for teams building trust-and-safety flows.
What You Can Integrate
MetaReach's API integration for matrimony platforms uses API key authentication, REST/JSON endpoints for OTP, WhatsApp, SMS, and IVR, and webhook callbacks for delivery status and verification-outcome events. A sandbox environment is available 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.
Setup
Common Pattern
Common Integration Pattern
Illustrative example only — actual field names and response formats are provided in full during onboarding.
Endpoints & Events
Beyond the four API surfaces above, most of the integration work happens in how endpoints and webhook events are shaped. Here's the pattern in more detail.
| Method | Illustrative Endpoint | Purpose |
|---|---|---|
| POST | /v1/otp/send | Trigger an OTP to a phone number |
| POST | /v1/otp/verify | Confirm the code a user entered |
| POST | /v1/whatsapp/message | Send a WhatsApp template or session message |
| GET | /v1/message/status/{id} | Poll delivery status for a specific message |
| POST | /v1/sms/send | Send a transactional/alert SMS |
Illustrative endpoint names only — actual paths, field names, and response formats are provided in full during onboarding.
Illustrative Webhook Event Payload
Webhook events typically cover delivery status (SMS/WhatsApp sent, delivered, failed), verification outcomes (OTP verified or expired), inbound WhatsApp replies, and call-completion events from IVR. Each webhook call includes a signature header so your endpoint can confirm the request genuinely originated from MetaReach rather than a spoofed source, and requests are built to be idempotent — safe to process more than once if a retry arrives after your system already handled the original delivery.
Authentication itself stays simple: every request carries your API key in a header, with sandbox keys scoped separately from production keys so a misconfigured test never reaches a real user. For signup and login flows, it's good practice to keep the OTP-send and OTP-verify calls on your server rather than calling them directly from a mobile client, so the API key itself is never exposed outside your own backend environment.
Sandbox & Timeline
Sandbox access is available before production, so verification and notification flows can be tested without real messages. Typical integration timeline for a basic OTP + notification setup: 1-3 weeks for a team familiar with REST APIs.
Go Further
The non-technical side of each tool this API powers.
Overview of signup and re-verification triggers.
Explore OTP VerificationMatch and interest notifications on WhatsApp.
Explore WhatsApp APIMatrimony platforms are technically SaaS products — see the parallel guide.
View SaaS/ERP GuideSee how matrimony platforms and bureaus use this infrastructure.
View Use CasesNeed the rest of the matrimonial communication stack? See the Matrimonial Messaging Solutions pillar for OTP, WhatsApp, SMS, IVR, and missed-call in one place.
Common Questions
Yes — sandbox testing doesn't require DLT registration or WhatsApp Business setup. DLT/PE registration applies to SMS (and applicable telecom voice) and is required only before production SMS sending; WhatsApp production sending requires a separate WhatsApp Business account with opt-in and approved templates, not DLT registration.
Yes — any event in your platform's logic can trigger the relevant API call.
1-3 weeks for basic OTP + notification flows; longer for full multi-channel orchestration including IVR.
Authentication is API-key based, passed with each request. Sandbox and production keys are issued separately, so you can build and test an integration without touching live channels or real recipients.
Failed webhook deliveries are retried automatically with backoff for a bounded period. As a longer-term safeguard, a status endpoint can also be polled so a missed webhook doesn't leave your platform without delivery or verification status.
Yes — endpoints are versioned, so existing integrations continue working unchanged when newer API versions are released.
Yes — rate limits protect platform stability for all customers. Our developer team shares your specific limits during onboarding, and the standard practice is to implement retry with exponential backoff whenever a request is rate-limited.
From startups to enterprises — brands that grow with MetaReach
