OTP & verification SMS
Short-lived codes and verification messages designed for login, signup and step-up checks.
SMS & Communication APIs
SMS API for OTP, transactional and marketing messaging
Integrate LOOKME SMS APIs into your mobile app, website or platform. Send OTP verification codes, transactional alerts and permitted marketing messages with delivery report webhooks across supported routes in India and internationally.
Available
lookme-api · SMS OTP
POST /v1/sms/otp
Authorization: Bearer <api_key>
{
"to": "+91XXXXXXXXXX",
"template": "otp_verify"
}
200 OK
{ "status": "queued", "message_id": "MSG_4412" }
REST
HTTPS JSON
SMPP
High volume
DLR
Delivery webhooks
Global
Scoped routes
SMS API infrastructure — not a messaging app
Product teams use LOOKME SMS APIs for account verification (OTP), order confirmations, payment alerts, appointment reminders and consent-based promotional campaigns. Every message is sent through your backend via HTTPS REST API or SMPP — you control the user experience.
Our communication stack includes JSON REST endpoints, SMPP connectivity for high-volume senders, template management, delivery report (DLR) webhooks, two-way inbound messaging and voice OTP fallback when SMS is not the preferred channel.
International and domestic routes are scoped per project based on destination country, traffic type, sender ID registration (including DLT in India), operator policies and partner coverage available for your engagement.
Important: Messaging services are provided subject to applicable telecom rules, anti-spam laws, operator policies, sender-ID registration and third-party provider terms. LOOKME does not send unsolicited traffic or guarantee delivery in every country.
Example API endpoints
Representative REST routes issued after onboarding. Paths and fields may vary per project.
Method
Path
Description
POST
/v1/sms/otp
Send one-time password for verification flows
POST
/v1/sms/send
Transactional or marketing SMS with template support
GET
/v1/sms/{id}/status
Query delivery status for a message
POST
/v1/sms/inbound
Configure two-way inbound keyword handling
POST
/v1/voice/otp
Voice fallback OTP when SMS is unavailable
SMS & communication capabilities
Capabilities your engineering team integrates through REST endpoints and webhooks.
Transactional SMS
Order, payment, reminder and system notifications with delivery callbacks where available.
Marketing SMS
Promotional messaging only where consent, local law and operator rules allow it.
Two-way SMS
Inbound numbers and keyword handling for support, opt-out and interactive flows.
Voice & voice OTP
Voice fallback for verification when SMS is not the preferred channel.
SMS API
HTTPS JSON APIs for send, status, templates and reporting, with server-side keys.
SMPP API
Higher-volume SMPP connectivity through approved partners where it fits the traffic profile.
International SMS
Multi-country routing scoped to destinations that can be supported for the engagement.
Multi-country infrastructure
Sender IDs, encoding, DLT-style registrations and route selection handled per market.
Webhook events
Signed HTTPS callbacks so your backend stays in sync without polling.
sms.delivered
Operator confirms message delivery to handset
sms.failed
Permanent or temporary failure with reason code
sms.inbound
User reply received on a two-way number
How integration works
Typical steps from enquiry to live API access.
-
01
Route discovery
Confirm destinations, traffic type, sender identity and compliance constraints.
-
02
API or SMPP design
Choose HTTPS, SMPP or a hybrid, including templates, webhooks and rate limits.
-
03
Sandbox & go-live
Test credentials, DLR handling and production cutover with monitoring.
-
04
Operate
Dashboards, alerts and ongoing route adjustments as volumes and markets change.
Integrate this API with LOOKME
Share your integration requirement, target markets and expected volumes. We will outline endpoints, webhooks and API access steps.