Skip to main content
Robase sends SMS through a pool of upstream gateways. You call one REST API; we pick the route for the destination country and fail over where a fallback is configured. Two products, same keys and credits: There is no public batch endpoint, template API, or list-messages API. Logs live in the dashboard. There is no public email API.

Phone numbers

E.164 only: +2348012345678. No spaces, no leading 0 without a country code. Invalid numbers return invalid_phone and are not charged. Benin (+229) numbers are 10 digits starting with 01, for example +2290196835987. The 0 stays after the country code. An older 8-digit number, or a number with that 0 removed, is invalid_phone and is not charged. Country is derived from the number. If we have no route, you get country_not_supported.

Sender IDs

New workspaces send transactional SMS under their own approved sender ID. Request your own sender ID any time from Sender IDs, after your first successful top-up. Approval usually takes 1 to 4 weeks. OTP goes out under Robase sender names after your first top-up, so you don’t need your own Sender ID for OTP. See Sender IDs.

Credits

Charged when the send is accepted (persisted), not when the carrier later reports delivered. If every provider fails, or anti-spam blocks the message, the credit is refunded. OTP is billed at the country’s credit rate (one message). Transactional SMS is billed at rate × segments. Cost per message depends on country and network. See live rates on the pricing page. Full table: coverage and pricing.

What we do not ship as a public API

  • SMS templates (POST /v1/sms with a template id)
  • Batch send (up to N messages in one call)
  • Sender-ID registration through the API (request it in the dashboard; see Sender IDs)
  • Simulator / test-mode keys