Add SMS to your product without building a telecom layer.
WorldText is programmable messaging infrastructure for SaaS and technology teams — one documented HTTP API for OTP, notifications, security alerts and workflow messaging, with real delivery receipts and a safe test mode.
REST API over HTTPS, documented endpoints, simulation for staging — the things engineers check before they trust a vendor.
Your event → WorldText API → your user
SMS · WorldText
Why teams stop building messaging in-house
Messaging looks simple on a diagram and becomes a project the moment deliverability, retries, receipts and regulations enter the room.
Your roadmap should not include a telecom layer
Deliverability tuning, retry logic, network quirks and receipt handling are an infrastructure distraction from the product you actually sell.
Dashboard-first vendors are not infrastructure
A campaign portal without a real API, without receipts and without a test mode is a tool for marketers — not a dependency for a product team.
Unreliable OTP costs you users
Authentication is a user-experience moment. Slow or lost verification codes mean abandoned sign-ups and support tickets you caused.
Product and campaign messaging need separation
Transactional alerts must not be mistaken for marketing. One API that keeps them distinct — with opt-out semantics where they belong — is the difference between messaging and spamming.
Your users are not in one market
A SaaS product serving international customers needs messaging that is verifiably reachable per market — not a provider that pretends 'global' covers everything.
Messaging that lives inside your product
Every use case below is triggerable from your own backend, worker, or workflow automation — and verifiable end to end.
OTP and authentication
Deliver one-time codes for sign-up, login and MFA — generated by your auth service, delivered by WorldText.
Workflow Auth event → code generated → API send → verified and expired
Security and account-activity alerts
Notify users on new-device sign-ins, password changes and unusual activity, the moment your system detects it.
Workflow Risk event → alert message → receipt recorded
Workflow and system notifications
Deployment results, job completions, failed pipelines and monitoring alerts — where engineers live, pings work.
Workflow CI/CD or monitoring event → notification → on-call sees it
User onboarding and lifecycle
Verification on sign-up, activation nudges and milestone updates — triggered by user state, not by a scheduler.
Workflow User state change → lifecycle message → engagement action tracked
API-triggered messaging
Call WorldText from any service — a single API call from your backend, queue worker or automation platform.
Workflow Any service → HTTPS call → message sent → callback receipt
Customer messaging and support
Give end users a way to reply to product messages — routing replies to your support stack.
Workflow User replies → routed to support queue → resolution message
How a message leaves your codebase
Straightforward by design, honest in the details.
Your service
Backend, queue worker or automation tool — wherever the event is already handled.
WorldText API
Documented endpoints over HTTPS with per-account credentials. Simulate first with &sim.
Mobile networks
Routed to the user's number per destination availability — see the coverage page.
Receipts back to you
Final delivery state returns to your callback URL: the integration sees what actually happened.
The API is documented end to end in our developer reference — including callback formats, message states and submission rate guidance.
What a real messaging API buys your product
Bought by engineering, felt by users.
Authentication flows that finish
Codes reach users promptly, and receipts tell you when they did not.
Notifications without the project
One integration covers OTP, alerts, lifecycle and workflow messaging — no platform built in-house.
Delivery visibility in your logs
Callback receipts flow into your own monitoring and enforcement logic.
Global users, one API
Add users in new markets without new messaging infrastructure or new vendors.
Marketing and transactional separated
Keep reachable, compliant product messaging distinct from campaign messaging.
Vendor risk you can review
Published API docs, SLA eligibility and documentation your team can actually audit.
Integration that reads like your own code
HTTP calls in — JSON-style receipts out. No SDK lock-in, no proprietary protocols required.
Call WorldText from any language or framework: your backend, serverless functions, queues, CI/CD pipeline or workflow automation platform. Because the interface is a documented HTTPS API, swapping providers later is a code change, not a migration project. Lower-level interfaces such as SMPP are also available for specialised integrations.
Connects to
Real endpoints, from our developer reference
API: https://sms.world-text.com/v2.0/sms/send Receipt states via your callback URL: ACCEPTD · DELIVRD · EXPIRED · REJECTD · UNDELIV Staging-safe testing without live delivery: &sim Submission rate guidance is documented per account.
Wire messaging into anything you can automate
Because WorldText is an API, messaging becomes one more step in workflows you already control.
Event-driven by default
Trigger sends from database changes, queues, webhooks or scheduled jobs — wherever your logic already runs.
Reply handling and routing
Inbound replies are passed to your URL or handled with rules — build a conversational loop in your own stack.
Retry and escalation logic
Use receipt states in your own automation: escalate undelivered OTP to an alternative channel, log failures to your queue.
AI-assisted messaging — your stack, our delivery
Generate or localise message content with your own AI tooling, then send via the API. WorldText delivers; you decide.
WorldText is not an AI platform, and it does not run autonomous conversations by itself. Anything above is assembled from the messaging API plus systems your team already operates.
Built for products with users everywhere
International by default, honest about the details.
International reach, per-market clarity
Send to users across markets; verify each destination on the coverage page before you ship the feature.
One API for product and internal messaging
End-user OTP, team alerts and workflow pings all go through the same endpoints.
Receipts your platform can consume
Callback URLs deliver final states — wire them into your own audit and alerting.
Throughput you can plan around
Documented submission rates per account, with higher throughput on request for launches and peaks.
What a technical buyer should check first
This section is the checklist — verify everything, and ask us about anything you cannot find.
Security
HTTPS transport, per-account API credentials, and documented handling of keys. Your authentication flow does not hand secrets to us — you send codes we never generate.
Data protection
Messages are processed under our Data Protection Agreement, with published retention, sub-processor and compliance documents.
Honest delivery states
ACCEPTD, DELIVRD, EXPIRED, REJECTD, UNDELIV — the exact final-state vocabulary of our callback, documented in the reference.
Responsible messaging
Transactional/product messaging and campaign messaging are distinct concepts — see the anti-spam policy and compliance guide for how they are handled.
Production-grade by design
API-first architecture, published SLA eligibility and a documented submission rate model — integration-friendly, not portal-first.
Engineer-to-engineer support
We answer integration questions at the level you asked them, and we publish the reference you can read without us.
One Tuesday in a SaaS product
An illustrative example of messaging working inside a live product — every message triggered by code.
User signs up
Your auth service generates a one-time code; WorldText delivers it via API within seconds.
Account verified
The code is entered, the account is created — no support ticket, no abandoned funnel.
New-device sign-in alert
Your security service detects an unusual sign-in; the user gets an alert and confirms it was them.
Nightly job fails
The on-call engineer is pinged by SMS — before the first complaint from a customer.
Receipts reconciled
Delivery states from every message have landed on your callback URL, in your logs, next to the events that triggered them.
Who owns messaging in your org
Different hats, different questions — all answered by the same API.
CTO
Messaging as a small dependency with a documented API — not a quarter-long internal project, and not a vendor lock-in.
Engineering lead
Clearly documented endpoints, real receipts and a simulation mode — integration time measured in hours, with tests to prove it.
Product manager
OTP, notifications and lifecycle messaging as product features — reliable by default, international without new work.
DevOps / reliability
Delivery states in your own monitoring, throughput guidance in writing, and a vendor that documents rather than vibes.
Frequently asked questions
The questions engineering teams ask before adding a dependency.
What does the actual API look like?
The API is documented end to end in the developer reference: base URL, endpoints such as /sms/send, parameters, callback formats and message states. Account credentials, stamps and delivery receipt examples are all published there.
What interfaces are available?
An HTTP REST API for most integrations, plus interfaces such as SMPP and email-to-SMS for specialised or legacy flows. The service pages and documentation describe each one.
What are the rate limits?
Submission speed guidance is documented per account in the API reference, and higher throughput can be requested — a conversation worth having before a big launch.
Can we test before release?
Yes. The API supports a simulation mode that processes messages without live delivery — ideal for staging, CI and load testing your integration beforehand.
Do the users of our app need to be in one country?
No. WorldText sends to international destinations with per-market availability shown on the coverage page — check the markets your users are in before launch.
How do delivery receipts work?
Configure a callback URL per account and every message reports a final state — accepted, delivered, expired, rejected or undelivered — so your systems can reconcile reality.
Can we send marketing messages through the same API as transactional ones?
Technically the same API serves both, but the two should be treated differently — consent, opt-out and content rules apply to campaigns. See our anti-spam and compliance guidance, and keep transactional messaging separate by design.
What about migrating from our current provider?
Because the interface is a documented HTTPS API, switching provider is typically an endpoint-and-credentials change in your own code. Our support team can review your integration to plan the cut-over.
Your product already knows when to message. Let it.
Add WorldText as the messaging layer behind your product — OTP, alerts and notifications with receipts your logs can prove. Read the reference, or talk to our team about your integration.
Related industries