Every message has an ID
Each accepted request returns a message ID. Use it to match delivery reports and to answer support questions with facts.
Text messaging for operations teams
Every message, accounted for.
Arken SMS gives operations teams a plain HTTP API for business messaging. Send over international routes, follow every message to its final delivery status, and pay from a prepaid balance you control.
Message record
Delivered- Message ID
- 4f9c2e1a-7b3d-4c8e-9a61-2d5f0b7e3c94
- To
- +61 491 570 156
- Route
- International
- Accepted by the API
- Sent to route
- Delivered to handset
01Platform
Everything you need to send, and nothing in the way.
Arken SMS is built for teams that send notifications, alerts and verification codes as part of daily operations, and need to know what happened to each one.
-
HTTP API
One authenticated request sends one message. JSON in, JSON out, standard HTTP status codes and readable errors.
-
Delivery reports
Status updates are posted to your webhook as each message moves forward, so your own records can follow along.
-
Per-customer API keys
API keys are issued with your account and tied to it alone. Store them server-side, out of reach of browsers and apps.
-
Prepaid credit
Sending draws from a balance you top up in advance, including by cryptocurrency, so costs follow the credit you load.
-
International routes
Send over international routes; we confirm your destinations before you start.
02Credit
Prepaid credit, topped up your way.
Your account holds a prepaid balance. Sending draws from it, so spend stays tied to the credit you load.
- Top up in advance, including with cryptocurrency.
- Plan top-ups around your expected sending volume.
- Ask sales about the top-up options for your account.
How credit works
-
Top upAdd credit to your account balance before you send.
-
SendEach message is charged against the balance.
-
Top up againAdd more credit before a busy period or a large send.
03Reliability
Where every message stands, at any moment.
Reliability is less about promises and more about knowing where every message stands. Arken SMS is built so your team can answer that question.
A final status, not a guess
Messages move through clear states and end as delivered or failed, reported to your webhook as they change.
Keys scoped to your account
An API key works for the one customer account it was issued to, and for no other.
Spend you plan in advance
Sending draws from your prepaid balance. You decide how much credit to hold and when to top up.
04API
One request sends one message.
Authenticate with your API key as a Bearer token and post a JSON body to the messages endpoint. That is the whole integration for sending.
Receive your API key
API keys are issued with your account.
Send a message
Post the recipient and the text to
/v1/messages.Store the message ID
The response carries an ID you will see again in every delivery report.
Receive reports
Point a webhook at your system and record each status update.
curl --request POST \
https://api.arkensms.site/v1/messages \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $ARKEN_TOKEN" \
--data '{
"to": "+61491570156",
"text": "Your order has shipped."
}'Run requests from your servers. An API key placed in browser or mobile app code can be read by anyone.
05Delivery reports
Know what happened to every message.
Register a webhook URL and Arken SMS posts a delivery report when a message changes status. Each report carries the message ID and its new status.
Step 1accepted
The API has validated your request and queued the message.
Step 2sent
The message has been handed to a route for delivery.
Finaldelivered
The route has confirmed delivery to the handset.
Finalfailed
The message could not be delivered. Failed messages are reported to your webhook.
Built for your records
Store reports next to your own data: order numbers, ticket IDs, account events. Your team answers "did it arrive?" from your own systems.
Simple to receive
Reports arrive as JSON over HTTPS at the URL you register, keyed by the message ID from your original request.
06Coverage and pricing
Where you send, and what it costs.
Share your destinations and an estimate of your volume. Coverage and pricing for your traffic are confirmed before you commit.
Coverage
International routes
Send over international routes; we confirm your destinations before you start.
Pricing
Pay as you go
You pay for the messages you send from your prepaid balance. Volume pricing on request.
07FAQ
Questions operations teams ask.
Who sets up a new account?
Our sales team does. Write to [email protected] with a few lines on your use case, the destinations you need and your expected volume.
How does the API authenticate requests?
Every request carries your API key as a Bearer token in the Authorization header. Each customer account has its own keys.
How do delivery reports reach my system?
You register a webhook URL. When a message changes status, Arken SMS sends a report to that URL with the message ID and its new status.
How does prepaid credit work?
You top up your balance in advance and each message is charged against it. Cryptocurrency top-ups are accepted. Ask sales about the options for your account.
Which destinations are covered?
Arken SMS works over international routes. Before your account goes live, sales checks each destination you plan to reach and confirms its price.
What does sending cost?
Pricing is pay as you go, charged per message from your prepaid balance. Volume pricing is available on request.
Can I choose the sender name?
Sender options depend on the destination and its rules. Ask sales about the destinations you need.
Ready when your team is.
Share your use case and the destinations you need, and sales will open your account and walk you through a first send.