Skip to main content
Create an account, add credits, request your sender ID, grab a key, send a code. Creating the account is free. Sending needs credits. Dashboard test sends are live traffic: they spend credits and reach a real phone. There is no simulator key prefix.
1

Create an account

Sign up at robase.dev/signup with Google, GitHub, or email. Verify the address if you used email. The setup wizard then asks for your business details.
2

Add credits

Top up in the wizard or under Billing (Paystack or Flutterwave). Your first successful top-up (minimum ₦600) adds bonus credits, once per account. Cost per message depends on country and network. See live rates on the pricing page.
3

Request your sender ID

New workspaces send transactional SMS under their own approved sender ID. Request it in the wizard: name, company documents, signature. 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.
4

Create an API key

Open API keys and create a key. The full token is shown once. It starts with robe_ followed by 64 hex characters.Store it as ROBASE_API_KEY. After the first view you only see the prefix.
5

Install an SDK (optional)

Prefer curl? Skip this step.
6

Send an OTP

A successful send returns status: "pending". Delivery is asynchronous. Poll GET /v1/otp/{id} or subscribe to otp.sent / otp.failed webhooks.
7

Verify the code

A wrong code with attempts remaining is 200 with valid: false. Terminal states (expired, already verified, attempts exhausted) return 409.

Send a transactional SMS

Same key, same routing. A new workspace needs an approved sender ID for the destination country first. Until then this call returns 422 sender_id_required and charges nothing.

Top up

Robase is pay as you go. Your first successful top-up (minimum ₦600) adds bonus credits, once per account. Top up again under Billing in the dashboard (Paystack or Flutterwave), or turn on auto top-up. Cost per message depends on country and network. See live rates on the pricing page.

Authentication

Bearer keys, robe_ prefix, no test-mode key scheme.

Webhooks

Delivery events signed with X-Robase-Signature.

OTP guide

Length, TTL, language, and verify semantics.

Transactional SMS

Segments, anti-spam, and status polling.