01
Connect your SMS provider
Use the Twilio adapter or configure an HTTP provider integration for services such as MSG91 and Fast2SMS. Provider accounts, sender approvals, and regional requirements remain your responsibility.
SMS NOTIFICATION API
SMS API for application updates.
Send SMS notifications through your configured provider with event templates, E.164 recipient validation, and delivery activity in one console.
- Recipients
- E.164 phone numbers
- Content
- Published SMS templates
- Request safety
- Idempotency-Key header
- Processing
- Background delivery
What the SMS engine handles for you
02
Publish an SMS template
Register the event, allow the SMS channel, and publish a template. Sendrin validates event data before accepting a notification.
03
Retry transient failures
Background delivery workers apply the configured retry policy. Circuit breakers pause calls to failing provider hosts; failed deliveries remain available for investigation.
04
Track delivery attempts
Inspect attempts, provider responses, and failure codes in the console. A successful API acceptance means queued for processing, not confirmed delivery to a handset.
SMS · request
POST /api/v1/notifications
Authorization: Bearer <SENDRIN_API_KEY>
Content-Type: application/json
Idempotency-Key: order-4821-shipped
{
"event_key": "order.shipped",
"channel": "sms",
"recipient": { "phone": "+919876543210" },
"data": { "order_id": "4821" }
}Supported providers
- Twilio
- MSG91 via custom HTTP
- Fast2SMS via custom HTTP
Before sending, configure and test your provider, register the event key, and publish its SMS template. Keep the API key on your backend. Provider fees and local sender-registration requirements are separate from Sendrin usage.
More in Messaging
INSTANT DEPLOYMENT
Your SMS providers, one API in front of them.
One API, every channel, full delivery visibility. Start free, no credit card required.