Skip to main content
The HTTP API is the simplest way to send an SMS — a single GET or POST request. The API key is passed as a parameter, not a header, so it works even where a platform can only issue GET/POST requests and cannot set a custom HTTP header.
The HTTP API is permanently supported — we will not discontinue it. For new integrations that need multiple channels (Viber/WhatsApp), fallback flow, or a structured response, we recommend JSON API v2.

​
Endpoint

For POST, send the parameters as application/x-www-form-urlencoded; for GET, as a query string.

​
Parameters

​
Authentication

Pass the API key as the apikey parameter — in the query string (GET) or the request body (POST). No header is required, which is the main advantage for integrations that can’t set custom headers.

​
Response

The response is text/plain, one line per recipient. Success (HTTP 200):
OK means accepted/queued, followed by the message_id and the phone number. Error:

​
Examples

​
Delivery receipts

Set a basic delivery webhook with the callback parameter (a URL). If you need the request shaped exactly for the target platform (method, headers, body), use the object-form callback in JSON API v2.