Cloud & Telecom Solutions

SMS API — Integration Guide Print

  • 42

WebTic SMS API — REST Integration Guide

The WebTic SMS API follows REST standards. Requests use JSON, with Bearer token authentication.

Main endpoint

POST https://api.webtic.online/v1/sms/send
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Request body

{
  "to": "+33612345678",
  "from": "WebTic",
  "body": "Your verification code: 483921",
  "callback_url": "https://votreapp.com/webhooks/sms"
}

Parameters

ParameterTypeRequiredDescription
tostringYesNumber in E.164 format (e.g. +33612345678)
fromstringYesSender (max 11 alphanumeric chars)
bodystringYesMessage content (160 chars = 1 SMS)
callback_urlstringNoWebhook for delivery receipt
validity_periodintNoExpiry in seconds (default: 72h)

HTTP response codes

CodeMeaning
200 OKSMS accepted — includes a message_id
400 Bad RequestInvalid parameters (badly formatted number, missing field)
401 UnauthorizedInvalid or expired API key
429 Too Many RequestsRate limit exceeded
500 Server ErrorServer-side error — retry

curl example

curl -X POST https://api.webtic.online/v1/sms/send \
  -H "Authorization: Bearer sk_live_abc123xyz" \
  -H "Content-Type: application/json" \
  -d '{"to":"+33612345678","from":"WebTic","body":"Your order is confirmed."}'

Webhook — Delivery receipt

{
  "message_id": "msg_12345",
  "status": "delivered",
  "timestamp": "2026-04-08T15:30:45Z",
  "code": "0",
  "description": "Message delivered to handset"
}

Delivery status codes

  • 0 — Successfully delivered
  • 1 — Failed: invalid number
  • 8 — Failed: blacklisted number
  • 25 — Failed: invalid Sender ID

Limits and best practices

  • One SMS = 160 characters (GSM 7-bit). Beyond that, the message is split into segments of 153 characters.
  • Special characters (€, non-GSM accents) switch to Unicode 16-bit encoding: limit reduced to 70 characters/SMS.
  • Implement a retry system with exponential backoff for 500/429 errors.

Was this answer helpful?

« Back