Request body

Try it

Send a request to see the response.

Example response

{ "success": "SMS sent successfully." }

Errors

Notes

• The OTP stays valid for 5 minutes.
• You can send at most 3 OTPs per phone number per hour (your own verified number is exempt).

Request body

Try it

Send a request to see the response.

Example response

{
  "user": {
    "uid": "f1e2d3c4-...",
    "identifier": "+213555123456",
    "country": "DZ",
    "createdAt": "2026-09-18T10:00:00.000Z",
    "lastLogin": "2026-09-18T10:02:13.000Z",
    "projectId": "my-project-id",
    "customerId": "<userId>",
    "type": "sms"
  }
}

Errors

Notes

• Only the latest OTP for that phone number is checked.
• On first success, a user record is created for that phone. Later verifications update the last login time.
• A successful check does not invalidate the OTP early — it remains usable until it expires.

Request body

Try it

Send a request to see the response.

Example response

{
  "success": "SMS sent successfully.",
  "encoding": "GSM-7",
  "smsLength": 47,
  "pduCount": 1,
  "cost": 7.5
}

Errors

Notes

• The template must be approved before you can send it.
• Placeholders look like {{name}}. Every required placeholder must have a non-empty value.
• You can send at most 5 fields; each value can be up to 40 characters.
• Cost is based on SMS segments. The response includes encoding, length, segment count, and cost. See SMS segments (PDU).

How we calculate

• 1. Choose encoding — If every character is in the GSM 7-bit default alphabet or its extension table, use GSM-7. If any character is outside that set (Arabic, emoji, …), use Unicode (UCS-2) for the whole message.
• 2. Measure length — GSM-7: each basic character = 1 septet; each extended character ^ { } \ [ ] ~ | € = 2 septets (escape + symbol). Unicode: length = number of UTF-16 code units (an emoji often counts as 2).
• 3. Count segments — GSM-7: 1 PDU if length ≤ 160, otherwise ceil(length / 153). Unicode: 1 PDU if length ≤ 70, otherwise ceil(length / 67). The lower multi-part sizes leave room for the concatenation header.

Limits

Examples

GSM 7-bit characters

Characters allowed in GSM-7. Click one to insert it into the tester. Anything outside this set forces Unicode.

Try it

References

• 3GPP TS 23.038 (ETSI TS 123 038) — Alphabets and language-specific information. Formerly GSM 03.38. GSM 7-bit default alphabet, extension table (escape 0x1B), and UCS-2. Single segment: up to 160 GSM-7 characters or 70 UCS-2 characters in 140 octets.
• 3GPP TS 23.040 (ETSI TS 123 040) — Technical realization of the Short Message Service. Formerly GSM 03.40. TP-User-Data up to 140 octets. Concatenated SMS (clause 9.2.3.24.1): 153 GSM-7 or 67 UCS-2 characters per segment with a standard 6-octet UDH.

Which codes can I use?

• SMS OTP and SMS notifications — only Algeria (DZ). The phone number must be an Algerian number (+213…).
• WhatsApp OTP — any country from the list below, as long as the phone number is valid for that country.
• Verify OTP — use the same country code you used when the OTP was sent.

All countries (245)

No countries match your filter.