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.
Zip SMS for settlement notifications
SveaSMS gives you a direct path to send bulk SMS in minutes — with tier-1 routing, real-time analytics and no KYC delay. Zip SMS for settlement notifications shows exactly how to get started.
- settlement notifications for Zip-connected apps
- REST + webhooks fan-out from your PSP events
- Idempotency keys — safe to retry
- Instant Sender ID, no ticket queue
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.
Scales with you
500 MPS by default, upgradeable on demand. From your first OTP to millions of marketing SMS per day — same infrastructure, same API, no migration.
GDPR-safe
Data is stored in the EU, with no subprocessors outside the EEA without explicit consent. A DPA is available on request and opt-out is handled automatically.
Frequently asked questions
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.
How is opt-out handled?
Automatically through STOP/AVSLUTA — the customer is placed on a per-sender blocklist. You can also whitelist.
Can I schedule campaigns?
Yes. From the dashboard or API, including timezone-aware scheduling and batch sends.
Do I need KYC or verification?
No. Sign up, top up and send. No forms, no application, no waiting.
Can I send OTP?
Yes. Low latency, high queue priority and separate throughput limits for transactional SMS.
Is SMS content logged?
Metadata is logged for DLR and support. Message content can be pseudonymized or deleted on request.