Multipurpose SMS API · Operator-managed pilot

One API.
Every update.
Stay in touch.

Connect your website or application to SMS. Send customer updates, alerts, reminders, announcements, and verification codes through one API.

Explore the API ↗See the flow

Self-hosted gateway. Separate application keys. No delivery claims before testing.

● ● ●POST /v1/sms
// Call from your application backend
curl "$TO1SMS_URL/v1/sms" \
  -H "Authorization: Bearer $TO1SMS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "+919876543210",
    "text": "Your order is ready for pickup."
  }'
202 · Message queued{ "message_id": "msg_example", "status": "queued" }

Illustration only. Accepted ≠ delivered.
REST API for your backendProject-scoped accessSingle messages + recipient lists
A familiar integration

Connect. Send.
Track the result.

Your application decides when to send. to1sms queues the message, paces the phone workers, and exposes delivery status.

01 / CONNECT

A key for every application.

The operator creates a project, assigns a phone pool, and issues a scoped API key. Store it on your server.

02 / SEND

Send one message or a list.

Send a notification to one number, or queue a list of up to 1,000 recipients. The gateway processes messages in the background.

03 / TRACK

Follow every batch.

Check queued, sent, delivered, and failed counts. Pause or cancel queued batch work from the operator console.

One service, many conversations

Built around your messages.

Trigger messages from your own application events, or send an operator-managed recipient list.

UPDATES & ALERTS

Keep customers in the loop.

Order updates, service notices, account alerts, and appointment reminders triggered by your application.

RECIPIENT LISTS

Reach a whole list.

Queue announcements and customer updates with recipient deduplication, paced sending, and batch progress controls.

OTP & VERIFICATION

Verify when it matters.

Send and verify single-use codes for login, signup, and account actions. OTP jobs take priority over ordinary messages.

Plan with real limits

How much can you send?

There is no unlimited SMS promise. Your approved route, carrier allowance, message segments, and online time determine capacity.

Illustrative inputs only. Enter a carrier-approved allowance. This calculator does not configure or enforce a sending limit.

Illustrative daily planning estimate90messages / day across these SIMs

floor(SIMs × approved segment allowance × availability ÷ segments per message). This is an allowance estimate, not a throughput benchmark or delivery guarantee.

India launch: confirm your business messaging route and applicable entity, header, and template registrations with your provider. Consumer SMS packs are not a commercial service capacity commitment. Read TRAI’s sender guidance ↗

Before you integrate

Clear expectations, from day one.

Is this ready for production traffic?

This release is a pilot foundation. Android enrollment and real delivery must be completed and tested before customers depend on it. No uptime or delivery SLA is offered here.

Can I use it with any framework?

Any server that can make HTTPS requests can integrate, including PHP, Laravel, Node.js, Python, and mobile application backends. Never ship a project API key in frontend code.

What does the service cost?

Public pricing is not set. Hosting, the approved messaging route, carrier charges, and support determine the operator’s costs. This page does not offer a paid plan or accept payments.

Does adding servers increase SMS delivery?

Backend processing and carrier delivery are different limits. This pilot should run as one gateway replica; multi-replica routing and end-to-end load tests are still required.

Build your integration

Start with the API.

Inspect the endpoints, then request a project key from your to1sms operator.

Read integration guide ↗