How do you send SMS via API without an SMS gateway?

Register an account, install the Android app on a phone with a SIM card and generate an API key in the dashboard. Then call POST /api/messages/ with the SMS body and recipient number. The message enters the queue and is sent from the SIM card via the carrier network - without an SMS gateway.

How is this platform different from traditional SMS gateways?

A traditional SMS gateway is an intermediary that charges per message plus a monthly fee. Here the SMS leaves from a physical phone with a SIM card - via the normal mobile carrier network, without an intermediary. Recipients see your number, and costs are limited to your phone subscription.

How much does it cost to send SMS via the API?

You pay a monthly licence fee for using the platform. The cost of sending each SMS is the cost of your phone subscription - no additional per-message charge. At high volumes this is significantly less than a traditional SMS gateway that bills per message.

How do I integrate the platform with my own application via REST API?

Add an HTTP call to your application: POST /api/messages/ with an Authorization header containing your licence key or API key, and a body with phone and message fields. Full documentation with examples for curl, Python and JavaScript is available at /docs/api.

Can I use my own phone number as the SMS sender?

Yes, that is the main advantage of this solution. The SMS leaves from the SIM card installed in the Android app - the number you control. Recipients see your personal or business number, not an anonymous gateway number. You can install the app on a dedicated business phone.

What is the API rate limit?

Rate limiting is configured per API key in the dashboard. The Android app fetches the queue of pending SMS messages every 15 minutes and sends with approximately 10 seconds between messages. This is a natural limit from sending via the carrier network. For high volumes, we recommend multiple phones with separate SIM cards.

LepszeSMSy

Send SMS via API - no SMS gateway fees

REST API integration for SMS delivery from your phone. Lower costs than traditional SMS gateways.

Try for free

Problems with traditional SMS gateways

SMS gateway charges per message plus a monthly subscription

Traditional SMS gateways bill per message and add a monthly subscription fee regardless of volume. Costs grow faster than your send volume.

Switching SMS providers means rebuilding your entire integration

Every gateway has a different API format, authentication parameters and response structure. Migrating between providers takes weeks of developer time.

No control over which number your SMS comes from

SMS gateways send from technical numbers or shortcodes that recipients do not recognise. Your own sender number increases trust and open rates.

High costs at large send volumes

When you are sending hundreds or thousands of SMS messages a month, gateway costs become a significant budget line. Higher volume does not lower the per-unit price.

How API integration works

1
Register an account and generate an API key in the dashboard. Install the app on an Android phone with a SIM card - that is your own sending channel.
2
Add a REST API call to your application: POST /api/messages/ with the SMS body and recipient number. Authorise with your licence key or API key.
3
The phone app fetches the queue every 15 minutes and sends SMS messages from the SIM card. You receive a webhook with a delivery confirmation on your endpoint.

What REST API integration gives you

REST API with full documentation and Swagger

Full API documentation available at /docs/api, interactive Swagger UI at /api/schema/swagger-ui/. POST /api/messages/ endpoint for single sends, bulk endpoint for up to 1000 SMS in one request.

SMS sent from a physical phone - your own sender number

Every SMS leaves from the SIM card installed in the Android app. Recipients see your phone number, not an anonymous shortcode. Higher open rates, greater trust.

No gateway fees - SMS via mobile carrier

Sending goes through the normal mobile carrier network, not a paid SMS gateway. You pay only for the phone subscription you already have.

Delivery status webhooks

After a message is delivered, the platform calls your HTTP endpoint with a status: delivered, failed or pending. You can react in real time inside your application.

Bulk API - send to 1000 recipients in a single request

POST /api/messages/bulk/ accepts a list of recipients with personalised content. One request queues a thousand SMS messages. Ideal for notifications, alerts and campaigns.

API keys per application, rate limiting and logs in the dashboard

Generate separate API keys for each integration. The dashboard shows send logs, delivery statuses and statistics per key. Rate limiting prevents accidental mass sends.

Frequently asked questions - SMS API

How do you send SMS via API without an SMS gateway?: Register an account, install the Android app on a phone with a SIM card and generate an API key in the dashboard. Then call POST /api/messages/ with the SMS body and recipient number. The message enters the queue and is sent from the SIM card via the carrier network - without an SMS gateway.
How is this platform different from traditional SMS gateways?: A traditional SMS gateway is an intermediary that charges per message plus a monthly fee. Here the SMS leaves from a physical phone with a SIM card - via the normal mobile carrier network, without an intermediary. Recipients see your number, and costs are limited to your phone subscription.
How much does it cost to send SMS via the API?: You pay a monthly licence fee for using the platform. The cost of sending each SMS is the cost of your phone subscription - no additional per-message charge. At high volumes this is significantly less than a traditional SMS gateway that bills per message.
How do I integrate the platform with my own application via REST API?: Add an HTTP call to your application: POST /api/messages/ with an Authorization header containing your licence key or API key, and a body with phone and message fields. Full documentation with examples for curl, Python and JavaScript is available at /docs/api.
Can I use my own phone number as the SMS sender?: Yes, that is the main advantage of this solution. The SMS leaves from the SIM card installed in the Android app - the number you control. Recipients see your personal or business number, not an anonymous gateway number. You can install the app on a dedicated business phone.
What is the API rate limit?: Rate limiting is configured per API key in the dashboard. The Android app fetches the queue of pending SMS messages every 15 minutes and sends with approximately 10 seconds between messages. This is a natural limit from sending via the carrier network. For high volumes, we recommend multiple phones with separate SIM cards.

Start sending SMS via API today

Set up your integration in minutes. No contracts, no gateway fees.

Try for free