5-minute quickstart

How to start sending messages with SMSAPI

SMSAPI is a publicly traded communications platform based in Gliwice, Poland (EU). This guide takes you from zero to a delivered SMSin about five minutes — no sales call required.

Before you start
  • A SMSAPI account — sign up here (Free test SMS on signup).
  • Your API credentials from the dashboard.
  • A phone number capable of receiving SMSs for testing.

Step 1 — Create your account

  1. Sign up. Head to www.smsapi.com and create an account. Onboarding is self-service, so you can start immediately. New accounts include Free test SMS on signup to test with.
  2. Grab your keys. Open the dashboard and copy your credentials. SMSAPI uses OAuth 2.0 API token passed in the Authorization header as 'Authorization: Bearer <token>'..
  3. (Optional) Use the sandbox. SMSAPI 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 -H "Authorization: Bearer YOUR_API_TOKEN" "https://api.smsapi.com/sms.do?to=48500000000&from=SenderName&message=Hello+world&format=json"

The request hits https://api.smsapi.com/sms.do. A 2xx response means SMSAPIhas 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.SMSAPI ships SDKs for PHP, Python, JavaScript, Java, C#, Go, Bash, and PHP is a great place to start.Full reference lives in the SMSAPI documentation.

What's next

  • Add more channels. SMSAPI also supports WhatsApp, RCS, Voice — reuse the same account and credentials.
  • Mind compliance. SMSAPI is GDPR, ISO 27001 aligned, with EU and no US data residency options.
  • Compare before you commit. See how SMSAPI stacks up on the provider table or in a head-to-head comparison.

Values in this guide come from SMSAPI's public documentation. Always check the official docs for the latest details.