Sending SMS - Robase

curl -X POST https://api.robase.dev/v1/sms/send \
  -H "Authorization: Bearer robe_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number": "+2348012345678",
    "message": "Your order #12345 has shipped.",
    "metadata": { "order_id": "12345" }
  }'

Field	Required	Notes
`phone_number`	yes	E.164
`message`	yes	Max six SMS segments (see segments)
`metadata`	no	Arbitrary JSON object, returned on GET

Response

200 with status: "pending". Delivery is asynchronous.

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "phone_number": "+2348012345678",
  "country_code": "NG",
  "credit_cost": 1,
  "segments": 1,
  "encoding": "gsm7",
  "sanitized": false,
  "status": "pending",
  "created_at": "2026-08-29T10:20:00Z"
}

Poll GET /v1/sms/{id} or wait for sms.sent / sms.delivered / sms.failed / sms.blocked. Status path: pending → sent → delivered, or failed, or blocked. The GET response also carries a timeline of each hop with a reason and a refund flag; see Delivery timeline.

OTP bodies

OTP messages are composed by Robase (workspace language, or language on the send). You do not pass a message on POST /v1/otp/send.

Not in this API

There is no template_id, no scheduled send, and no /v1/sms/batch. Loop with idempotency keys if you need many destinations.