Skip to main content
JSON API v2 is SmsManager’s primary API for sending messages across SMS, Viber, and WhatsApp. Every request is authenticated with your API key, and most endpoints accept a JSON body that lets you target up to 10 recipients, define multi-channel flows, schedule delivery, and receive delivery callbacks. If you are migrating from an older integration, note that JSON API v1, the HTTP API, and the XML API are all deprecated — you should use v2 for all new work.

​
Base URL

All endpoints in this reference are relative to this base URL.

​
Authentication

JSON API v2 uses API key authentication. For all POST endpoints, pass your key in the x-api-key request header:
The GET /simple/message endpoint is the only exception — it accepts the key as an apikey query parameter instead of a header. You can find your API key in your account settings. Keep your key private; anyone who holds it can send messages on your behalf. For a broader explanation of authentication across SmsManager APIs, see the Authentication guide.

​
Endpoints summary

​
Request format

POST /message and POST /messages expect a Content-Type: application/json body. The /simple/message endpoints use query parameters (GET) or application/x-www-form-urlencoded (POST) respectively.

​
Common request fields

The following fields are shared across POST /message and POST /messages. Each message object you send can include any combination of them.
JSON API v1 is deprecated. All new integrations should target JSON API v2 (https://api.smsmngr.com/v2). The HTTP API and XML API are also deprecated.

​
Explore the endpoints

Individual endpoints — with parameters, request bodies, and examples — are listed in this section’s sidebar, generated directly from the OpenAPI specification.