Developer-friendly API
Simple REST API with idempotency keys, webhooks for DLR and incoming SMS, plus examples for Node.js, Python, PHP, Go and Ruby. Send your first SMS with curl in under 60 seconds.
SMS API in China
SveaSMS gives you a direct path to send bulk SMS in minutes — with tier-1 routing, real-time analytics and no KYC delay. SMS API in China shows exactly how to get started.
- SMS API tuned for China (+86)
- Local carrier partners with tier-1 delivery
- REST API, dashboard and CSV upload
- Crypto and card top-ups
- Real-time DLR & analytics per message
Your own Sender ID
Set any sender name you want, up to 11 alphanumeric characters. No pre-approval, no waiting, no follow-up questions. Change Sender ID between campaigns or use different IDs per segment for A/B testing.
Delivery rate that holds
Direct connections to Telia, Telenor, Tre and Tele2 provide stable delivery to Swedish numbers. Real-time DLR shows exactly which SMS were delivered, pending or bounced — nothing sits in dark queues.
No KYC or application
Other platforms force you through weeks of verification before the first SMS. We do not. Sign up, top up, send. That simple.
Frequently asked questions
Can I schedule campaigns?
Yes. From the dashboard or API, including timezone-aware scheduling and batch sends.
Can I choose any Sender ID?
Yes. Set any sender name you want, up to 11 characters. We do not pre-review Sender IDs for you.
Is SMS content logged?
Metadata is logged for DLR and support. Message content can be pseudonymized or deleted on request.
Can I send OTP?
Yes. Low latency, high queue priority and separate throughput limits for transactional SMS.
How is opt-out handled?
Automatically through STOP/AVSLUTA — the customer is placed on a per-sender blocklist. You can also whitelist.
Can I use multiple Sender IDs at once?
Yes. Rotate per segment, campaign or language with no hard cap.