One call to send
Pass recipients, text and sender name. The job is accepted immediately and every message gets its own identifier and its own status.
Developers
SMS API
One key, sent from your server, covers sending, scheduling and reading statuses. Nothing to install, no SDK you are forced to adopt, and the same published price per segment as the workspace.
- 40 topics
- One key
- No SDK required
- Live in 5 minutes
Statuses come back
Each message keeps a status that updates as networks report, so your system reconciles without guessing.
Same pricing
Published price per segment in EUR per destination, whether the message came from the screen or from your code.
Keys you control
One key per integration. Create, deploy, then revoke the old one. No downtime if you do it in that order.
Getting started
Message support on Telegram at @exerioco, get the account opened and create a key in the workspace the same day.
FAQ
Do I need a library?
No. Any language that can make an HTTPS request can send.
Is API pricing different?
No. Same published price per segment as the workspace.
How do I get a key?
Message support on Telegram at @exerioco, then create the key in your workspace.
Related pages
SMS APIOne call sends a message to one recipient or to thousands.API authenticationEvery request carries your key.Managing API keysCreate, rotate and revoke keys.Bulk sendingThousands of recipients in one request.Delivery reportsRead the status of every message.Scheduled sendingQueue a send for later from code.Balance and creditsCheck what is left before you send.Prices per destinationKnow the cost before the send.Segment countingWork out the size before sending.Sender names in the APISet the name per request.Error handlingWhat to do when a call fails.Retries and idempotencyAvoid sending twice.Status valuesThe statuses a message moves through.Number validationClean numbers before you send.Importing listsTurn a file into a send.Unicode messagesSending emoji and non latin text.Long messagesWhat happens beyond one segment.ThroughputHow fast a large send moves.Queueing behaviourWhat happens between send and delivery.TimeoutsSetting sensible limits.HTTP interfaceA plain HTTP call, no library needed.JSON payloadsThe shape of a request.Testing an integrationTry it without a campaign.Logging and auditKnow what your system sent.Securing callbacksVerify anything that calls you.Codes over the APIVerification at speed.Alerts over the APIMachine generated warnings.Reminders over the APIScheduled from your own calendar.Ecommerce integrationsOrder events into messages.CRM integrationsSending from your customer record.Product notificationsMessaging inside your product.Marketing automationSMS as a step in a flow.VersioningKeeping an integration stable.Securing the integrationWhere the key belongs.Restricting accessLimiting where calls come from.Monitoring your integrationNoticing a problem early.Reconciling spendMatching your records to ours.Sending to many countriesOne integration, every destination.Practical limitsHow much can go in one request.Getting API accessHow to start.
Build with it today
Support on Telegram at @exerioco answers integration questions in minutes.