Skip to main content
Credits are prepaid and cover SMS OTP, WhatsApp OTP, and transactional SMS. One credit has a fixed price; a message costs a number of credits that depends on where it lands, and on which network answers for the number. GET /v1/pricing publishes the table that bills your messages. It needs no API key, and it is the same table the price page and the dashboard read. While VAT collection is on, the response adds vat_rate_bps (750 is 7.5%) and prices_exclude_vat: true. The price page and pricing.md then label those prices ”+ VAT”. VAT on a credit top-up is charged on the credit price. The payment processing fee is separate and is not part of the VAT base. While collection is off, both fields are absent and the pages stay as they are. seller_tax_id is not included.

Reading a country

Countries are ordered cheapest first. min_credits and max_credits are equal where every number to a country costs the same. Where they differ, the rate depends on the recipient’s network: a Nigerian number on Glo costs 3 credits, and one on any other network costs 1. An unlisted destination is still sendable and still charged at the price shown. The +1 territories are routed so those numbers keep working, and they are not destinations Robase markets.

What you are actually charged

Two things decide the charge on a send:
  1. The network. Robase identifies the recipient’s network from the number and applies that telco’s rate. When it cannot, the country’s credits applies.
  2. The parts. A long message is split by the carrier and billed per part, so a two-part message to Nigeria costs two credits, not one. See Segments and encoding.
The response to POST /v1/sms/send carries the credit_cost that was actually charged, along with segments.

WhatsApp OTP credits

whatsapp is a parallel array of { country_code, country_name, credits, price } computed at request time from whatsapp_otp_costs plus FX:
Same formula as send. The wildcard row * is the platform default. Destinations without a cost row are not free: WhatsApp send is refused until priced. WhatsApp is OTP-only (Meta Authentication + copy-code), not general messaging.

Custom Sender ID credit gate

sender_id_requires_purchase is true: a workspace must complete at least one credit purchase before it may request a custom Sender ID. See Sender IDs.

First top-up bonus

first_topup_bonus_credits is an integer on this response. It is the one-time grant added on the first successful top-up, once per account. It is 0 when that bonus is off. Creating an account does not add credits. The price list and the dashboard promo read the same platform setting.

Caching

Prices change rarely. The endpoint sets Cache-Control: public, max-age=60, and the server holds a built table for the same minute, so polling it more often than that returns the same answer. first_topup_bonus_credits is part of that table, so a change to the bonus setting shows up within the same minute.