MSG91 API

Name: MSG91 API
Brand: MSG91 API
Availability: InStock

✓ Official Vendor SpecCommunicationsSms MessagingapiKey76 EndpointsREST

For Agents

Send SMS, email, WhatsApp, and voice messages, run OTP verification, and manage contact campaigns through MSG91's multi-channel communications API.

Install Jentic One Beta

Connect the MSG91 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MSG91 API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MSG91 API.

Send and verify one-time passwords across SMS and email channels via /v5/otp and /v5/otp/verify

Trigger transactional flow templates with dynamic variables via POST /v5/flow

Pull SMS delivery logs and analytics via /v5/report/sms/logs and /v5/report/sms/analytics

GET STARTED

Start building with MSG91 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MSG91 API for, with concrete tasks.

★ OTP-Based Login and Signup

Consumer apps issue one-time passwords during signup and login to verify phone ownership without storing passwords. MSG91's /v5/otp endpoint sends the code, /v5/otp/verify validates the user's input, and /v5/otp/retry reissues if the SMS is missed. The dedicated OTP routing tier delivers in seconds across Indian carriers, which is why the same flow powers most fintech and ride-hailing onboarding stacks in the region.

Call POST /v5/otp with the user's mobile number, then call GET /v5/otp/verify with the submitted code and reject the signup if the response indicates a mismatch.

Transactional SMS Flows for Order Updates

E-commerce and logistics platforms send order-confirmed, out-for-delivery, and delivered notifications as transactional SMS. MSG91's /v5/flow templates accept dynamic variables, so a single approved DLT template covers every order without per-message content review. The /v5/report/sms/logs endpoint exposes delivery state for reconciliation against the order pipeline.

Call POST /v5/flow with the approved template id and the order variables, then audit deliveries via POST /v5/report/sms/logs filtered to that flow id.

WhatsApp Template Notifications

Customer engagement teams send WhatsApp template messages — appointment reminders, shipping notifications, invoice receipts — through the MSG91 WhatsApp integration. Templates are pre-approved with Meta and the API attaches dynamic variables at send time. This is the primary channel for high-engagement notifications where SMS deliverability or open rates are insufficient.

Send a 'shipment_dispatched' WhatsApp template to the customer's number with order id and tracking link as template variables.

Agent-Driven Multi-Channel Outreach

An AI agent runs an outreach playbook that escalates from email to SMS to WhatsApp until the recipient engages. Through Jentic the agent searches for 'send a transactional sms', 'send a whatsapp template', and 'send an email' and gets a single auth flow across MSG91's email, SMS, and WhatsApp endpoints. Channel fallback is one configuration step instead of three integrations.

Search Jentic for 'send a transactional sms', execute POST /v5/flow, and on no-engagement after 24 hours fall back to a WhatsApp template send through the same agent flow.

Key Endpoints

76 endpoints — msg91 is an india-headquartered cloud communications platform that exposes sms, otp, email, whatsapp, rcs, and voice messaging through a single api alongside segmento contact management and campaign tooling.

METHOD

PATH

DESCRIPTION

POST

/v5/otp

Issue a one-time password to a phone number

GET

/v5/otp/verify

Verify a submitted OTP

POST

/v5/flow

Trigger a transactional flow template

POST

/v5/report/sms/logs

Pull SMS delivery logs

GET

/v5/report/sms/analytics

Retrieve SMS analytics aggregates

GET

/v5/report/otp/analytics

Retrieve OTP analytics aggregates

POST

/v5/otp

Issue a one-time password to a phone number

GET

/v5/otp/verify

Verify a submitted OTP

POST

/v5/flow

Trigger a transactional flow template

POST

/v5/report/sms/logs

Pull SMS delivery logs

GET

/v5/report/sms/analytics

Retrieve SMS analytics aggregates

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The MSG91 authkey is stored encrypted in the Jentic vault and injected into the authkey header at execution. Agents receive a scoped session token — the raw key never enters prompt context or logs.

Intent-based discovery

Agents search Jentic with intents like 'send an otp' or 'send a whatsapp template' and Jentic returns the matching MSG91 operation with its input schema, hiding the channel-specific path conventions.

Time to first call

Direct MSG91 integration: 2-3 days to handle channel routing, DLT template approval, and webhook setup. Through Jentic: under an hour to send a first transactional SMS or OTP.

FAQs

Specific to using MSG91 API through Jentic.

What authentication does the MSG91 API use?

The MSG91 API uses an API key passed in the authkey header. Through Jentic the authkey is stored encrypted in the vault and injected at request time, so it never appears in the agent's prompt context.

Can I send and verify OTPs in one workflow?

Yes. POST /v5/otp issues the code to the supplied mobile number and GET /v5/otp/verify validates the user's submitted code. /v5/otp/retry resends the code if the user does not receive the first message.

What are the rate limits for the MSG91 API?

MSG91 enforces channel-specific throughput tied to your account class — DLT-approved transactional SMS routes burst higher than promotional routes, and WhatsApp respects the Meta tier on your number. Spread campaign sends across the /v5/flow endpoint with batching to avoid throttling.

How do I trigger a transactional SMS flow through Jentic?

Search Jentic for 'send a transactional sms', load the /v5/flow schema, and execute POST /v5/flow with the approved DLT template id and your variables. The agent receives the delivery acknowledgment without ever holding the authkey.

Is the MSG91 API free?

MSG91 offers free trial credits for evaluation but production use is metered per channel — SMS by sender route and country, WhatsApp by Meta conversation tier, voice per minute. Check the dashboard for active rates before launching a campaign.

Does MSG91 support WhatsApp templates?

Yes. The WhatsApp endpoints send pre-approved templates with dynamic variables and ingest inbound replies on the configured webhook. Approval flows through Meta's Business Manager and templates appear in the dashboard once live.

MSG91 API

Connect the MSG91 API to your agent

Capabilities

Start building with MSG91 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs