Send with one request
Pass recipients, text and a sender name. Each accepted message receives its own identifier and delivery status.
Developers and automation
Free API access for bulk SMS
Create your account and API key immediately. Send one message or millions from your own system, with no required SDK, custom Sender IDs and the same clear destination pricing as the workspace.
NO KYCFree API accessCustom Sender IDs99% delivery rateWorldwide coverage
- 40
- Free API access
- No SDK required
- Custom Sender IDs
- Worldwide SMS
Live delivery statuses
Read message status as networks report back, so your system can reconcile every send without guessing.
No separate API fee
API access is included. You pay only the published destination price for the SMS traffic you send.
Keys you control
Create a separate key for each integration. Replace or revoke keys from your account whenever needed.
Start without approval
Register with email and password, add credits and create your first key. No KYC, sales call or account approval queue.
FAQ
Do I need a library?
No. Any language that can make an HTTPS request can send SMS.
Does API access cost extra?
No. There is no separate API platform fee. You pay only for the SMS traffic you send.
How do I get a key?
Create an account, open API keys in your workspace and generate a key immediately.
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 eXerio today
Create your account and first API key in minutes. Telegram support is available for integration questions.