API reference

A small REST API over HTTPS, JSON in and JSON out. Six endpoints: send, read status, list, check balance and pricing, plus a webhook you can receive.

Base URL

https://api.splashifypro.com/api/v1/sms

Every path in this reference is relative to that. HTTPS only.

What the API is for

Sending, and reading what happened. Registration stays in the panel.

What an API key can reach.
Field	Type	Description
`Send a message`	POST /messages	The main endpoint.
`List a day of messages`	GET /messages	Newest first.
`Read one message`	GET /messages/{id}	Current status and detail.
`Check balance`	GET /balance	Wallet, in rupees.
`Check pricing`	GET /pricing	Your price per part, per category.

Registering entities, sender IDs and templates, and creating API keys, are panel-only. They are declarations made in your company's name under DLT, so they need a signed-in person rather than a credential in a config file. An API key attempting one gets 403.

Conventions

Field	Type	Description
`Content type`	application/json	On every request with a body. Responses are always JSON.
`success`	boolean	Present on every response. Check it as well as the HTTP status.
`message`	string	Present when something went wrong, written to be shown to a person as-is.
`Times`	RFC 3339, UTC	Convert to IST for display if you need to.
`Money`	number, rupees	A per-part price can have four decimal places, so do not round it to two before multiplying.

A first request

curl https://api.splashifypro.com/api/v1/sms/balance \
  -H "Authorization: Bearer sms_live_your_key_here"

{ "success": true, "balance": 1250.5, "currency": "INR" }

If that works, your key is valid and your account is reachable. See Authentication to create one.

Rate limits

Sending is rate limited per account. A burst that exceeds it gets 429; wait briefly and retry rather than retrying immediately.

Balance and pricing are not limited alongside sending, so checking your balance before each message is fine and is encouraged for long campaigns.

What to store on your side

The message_id from every send. It is how you look a message up later and the one thing support needs to investigate.
The parts count, if you reconcile spend yourself. It is the billing unit.

You do not need to store the message text; it is on the message record for 90 days.

API reference

Base URL#

What the API is for#

Conventions#

A first request#

Rate limits#