How to start sending messages with seven.io
seven.io is a privately held communications platform based in Kiel, Germany (EU). This guide takes you from zero to a delivered SMSin about five minutes — no sales call required.
- A seven.io account — sign up here (€0.50 free test credit).
- Your API credentials from the dashboard.
- A phone number capable of receiving SMSs for testing.
Step 1 — Create your account
- Sign up. Head to www.seven.io/en and create an account. Onboarding is self-service, so you can start immediately. New accounts include €0.50 free test credit to test with.
- Grab your keys. Open the dashboard and copy your credentials. seven.io uses API key sent in the X-Api-Key request header (separate sandbox API keys available for testing).
- (Optional) Use the sandbox. seven.io offers a test environment, so you can validate your integration before sending live traffic.
Step 2 — Send your first SMS
The fastest path is a single API call. Drop in your credentials and a destination number, then run this from your terminal:
curl -X POST https://gateway.seven.io/api/sms \
-H "X-Api-Key: YOUR_API_KEY" \
-H "Accept: application/json" \
-d "to=49176123456789" \
-d "from=AcmeInc" \
-d "text=hello world"The request hits https://gateway.seven.io/api/sms. A 2xx response means seven.iohas accepted your message for delivery — you should see it arrive within seconds.
Step 3 — Go native with an SDK
Once the raw call works, switch to an official SDK for retries, typing and error handling.seven.io ships SDKs for PHP, JavaScript, Python, Go, Ruby, .NET, Rust, Kotlin, Elixir, Swift, and PHP is a great place to start.Full reference lives in the seven.io documentation.
What's next
- Add more channels. seven.io also supports WhatsApp, RCS, Voice — reuse the same account and credentials.
- Mind compliance. seven.io is GDPR, ISO 27001 aligned, with EU and no US data residency options.
- Compare before you commit. See how seven.io stacks up on the provider table or in a head-to-head comparison.
Values in this guide come from seven.io's public documentation. Always check the official docs for the latest details.