Skip to main content
Recipients see an alphanumeric sender ID when the upstream carrier accepts one.

Who needs one

New workspaces send transactional SMS (POST /v1/sms/send, dashboard test sends and retries) under their own approved sender ID in every country that offers custom sender IDs. 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. The setup wizard offers it as an optional step 3, and you can skip it if you only send OTP. POST /v1/otp/send uses those Robase sender names. Existing workspaces keep their current setup. They can send as Robase (the default) or RAlerts without a request, and can still request their own name. Messages to a country where custom sender IDs are not open go out under the platform name.

When a send is refused

A new workspace with no approved sender ID for the destination country gets this from POST /v1/sms/send:
The status is 422. The check runs before any charge, so nothing is charged. Request a sender ID from Dashboard → Sender IDs, or send to a country where custom sender IDs are not open. See Errors.

Countries

Country notes:
  • Nigeria: along with the CAC certificate, give your TIN or upload a TIN confirmation or NRS taxpayer registration acknowledgement. Either works alongside your CAC certificate. A tax certificate is not required.
  • Kenya: no religious, political, gambling or adult content.
  • Tanzania: every sample message must contain the sender ID.
  • South Africa: some networks may replace the sender name.
  • Côte d’Ivoire and Benin: French documents are accepted.
Uploads are PDF, JPEG, PNG or WEBP, 1 MB at most. Photos over that size are reduced in the browser before they are sent.

Request your own name

Requests need at least one successful credit purchase. Bonus credits do not count. From Dashboard → Sender IDs → Request a Sender ID (or step 3 of the setup wizard):
  1. Name. Pick the country, choose the sender name and the category: one-time passcodes, transactional or banking. Describe the use case and add one to three sample messages. The dashboard checks the name against the carrier rules as you type.
  2. Company. Upload your registration certificate. We read the company details from it, and you confirm them. Add the tax ID (in Nigeria, the TIN, or a TIN confirmation or NRS registration letter), your expected monthly volume, the address, and the documents your country needs (see the table). Give the details of the authorised representative.
  3. Authorize. Sign once, drawn or typed, and add your company stamp if you have one. Give the signatory’s phone number; it is printed on the letters. Add your company letterhead: upload an image of it (PNG or JPEG), or, if you have none, make one in the dashboard from your company details and adopt it. You can add your logo (optional) for the letterhead maker. A request cannot be submitted without a letterhead. We prepare and file the carrier letters on your behalf.
You then see the request move through Submitted → In review → Filed with carriers → Approved, on the request page and by email. If something needs fixing, the request comes back as Needs changes with the reason, and you edit and resubmit. If the use case is lending (loan messages), the request must include one lending licence. Any one of these is enough: a CBN approval, an FCCPC approval, or a state money lender licence. The networks reject an application that does not have one. Other use cases do not need this document. It is separate from the country documents in the table below. A CBN licence for the banking category does not take the place of the lending licence. The licence is uploaded like any other sender ID document, before the use case is saved as lending. The document type is cbn, fccpc, or state_money_lender. Saving a lending use case, removing the last of those documents, or submitting (including after needs changes) without one returns 422:
code is stable. error is the sentence. The networks set the pace. The times in the table are usual, not promised.

Rules

  • 3 to 11 letters or numbers, at least one letter, no spaces or symbols. The name matches ^[A-Za-z0-9]+$ (minLength 3, maxLength 11). A name that does not match is refused with 400 sender_id_invalid and the message “Use 3 to 11 letters or numbers, at least one letter, no spaces or symbols.” A name that passes is stored in capitals.
  • The name must relate to your business, product or service. No personal names, no brands you do not own, and no generic or reserved names.
  • The company on the registration certificate must own the name.
  • Each request is for one country. A workspace with an approved name in one country can request a name for another country.
  • An approved name is used for messages to its country.

Not in the API

There is no public sender-ID endpoint. You cannot register, list, or pick a sender ID with the customer API. POST /v1/sms/send and POST /v1/otp/send use the sender the workspace is set up with. Transactional OTP traffic is routed on transactional paths so Nigeria’s NCC DND registry is not treated as a promo filter for one-time passcodes. See DND compliance.