Ja. REST API med exempel för Node.js, Python, PHP, Go och Ruby. Se /api/rest för dokumentation.

Loggas SMS-innehåll?

Metadata loggas för DLR och support. Meddelandeinnehåll kan pseudonymiseras eller raderas på request.

Ja. Låg latens (sub-3s), hög prioritet i kön och separata throughput-limits för transaktions-SMS.

Kan jag schemalägga utskick?

Ja. Via dashboard eller API — inklusive tidszons-medveten schemaläggning och kvartalsbatcher.

Kan jag använda flera Sender IDs samtidigt?

Ja. Rotera per segment, per kampanj eller per språk — helt utan tak.

Behöver jag KYC eller verifiering?

Nej. Registrera, fyll på saldo, skicka. Inga formulär, ingen ansökan, ingen väntetid.

SveaSMS – also written Svea SMS, Svea sms or svea-sms – is a global bulk-SMS platform for senders in 200+ countries.

Virtual numbers

OTP codes and two-factor on Notion

SveaSMS gives you a direct path to send bulk SMS in minutes — with tier-1 routing, real-time analytics and no KYC delay. OTP codes and two-factor on Notion shows exactly how to get started.

Numbers in 190+ countries — live stock
No KYC, no SIM card, no contract
Codes appear in your inbox in real time
Automatic refund if no code arrives
Pay with crypto or card
Same account as bulk SMS and the API

Transparent pricing

One price per SMS, no monthly fee, no lock-in contract. Balance never expires and you see the exact campaign cost before you press send.

Support that answers

We operate from Sweden. Ping us and a technician answers — not a chatbot, not a tier-1 agent escalating. Directly to someone who knows the system.

Real-time analytics

See delivery rate, click rate, opt-outs and revenue per campaign in real time. Segment by operator, geography and time of day — then export to your data lake with webhooks or CSV.

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.

Frequently asked questions

Is there an API?

Yes. REST API with examples for Node.js, Python, PHP, Go and Ruby. See /api/rest for documentation.

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.

Can I schedule campaigns?

Yes. From the dashboard or API, including timezone-aware scheduling and batch sends.

Can I use multiple Sender IDs at once?

Yes. Rotate per segment, campaign or language with no hard cap.

Do I need KYC or verification?

No. Sign up, top up and send. No forms, no application, no waiting.