In brief
- Send short text (9 to 160 characters) to one or many numbers.
- Query history or a single send by id.
- Cancel while status is
QUEUEDorSCHEDULED.
Before you start
Base URL:
https://api.notifique.dev. Replace sk_live_xxxxx with your key (sk_test_... in sandbox).
1. Send SMS
to is always an array (up to 500 recipients).
messageIds.
Fewer than 9 characters in
payload.message → 400 (SMS_MESSAGE_TOO_SHORT).Send with template
If you already have a workspace template with SMS enabled, usetype: "template", the same pattern as WhatsApp, Telegram, and other channels:
2. List history
3. Query one send
sms:read.
4. Schedule and cancel
Schedule, include on the send POST:QUEUED or SCHEDULED):
sms:cancel.
5. Pick the send type
options.speed sets the carrier route and changes the price. In the dashboard: SMS → New SMS → Send type (SMS Full, SMS Standard, SMS Slow).
full:
from (your active purchased line), recipients see your number. Price varies by country (smsOwnNumber in GET /v1/pricing) — options.speed does not apply.
A value outside the list returns 400 (options.speed must be full, standard, slow).
6. Avoid duplicates
Idempotency-Key header on POST. Retries within 24 h do not create duplicate sends. See Security and reliability.
7. Webhooks (optional)
Set upsms.sent, sms.delivered, sms.failed, and MO (sms.received, sms.replied) to track without polling.
Guide: Webhook events.
8. Localization and variables
localization(off|manual|ai) +i18ntranslatepayload.messageper recipient.- Root
variablessubstitute{{placeholders}}in free text. - 202 response may include
data.localization,data.sandbox, anddata.smsSkippedRecipients.
All send types
In the API reference (SMS tab), open Send SMS (POST /v1/sms/messages) and use the playground examples:
Without
speed in the body, billing uses standard.
Next steps
- Introduction: when to use and status lifecycle
- Scopes: key permissions
- Webhook events: real-time status
- Error responses: HTTP codes and
code

