Skip to main content

Going live

You can integrate in Test mode as soon as you sign up. To book real deliveries, complete the activation checklist in the dashboard and let Reeds review your account.

Sign up and activate​

  1. Sign up with your first and last name, business name, work email, Nigerian mobile number and a password. Say what you want to do with Reeds: ship your business's orders, offer Reeds delivery to merchants on your platform, or sell online with a Reeds store.
  2. Verify your email address (a link) and your phone number (an SMS code).
  3. Start in Test mode. Your account opens in the dashboard with a ₦100,000 test wallet. Create your test credentials under Developers.
  4. Work through the activation checklist on the dashboard home page:
StepWhat you provide
Business typeStarter (not yet registered) or Registered with CAC. Registered businesses only enter their CAC number.
Business profileCategory, description, website or social handle, and expected monthly deliveries
Pickup locationAt least one pickup location, picked with Google Places and checked against Reeds' coverage
Owner identityA copy of the owner's government ID: national ID card, international passport, driver's licence or permanent voter's card
BillingConfirm you'll pay from a prepaid wallet. You can fund it at any time.
  1. Wait for review. Reeds reviews your submission, usually within one working day.
  2. Go live. On approval, Live mode switches on, you can create live credentials, and you get an email.
note

Platform accounts are not self-serve. If you ship for many merchants, apply for a platform account from the dashboard. See Platforms.

Go-live checklist for developers​

  • Create live credentials in Dashboard → Developers and store them as server-side secrets. See Authentication.
  • Switch your client id and secret to the rci_live_ and rcs_live_ values. The base URL stays the same.
  • Consider restricting live credentials by IP. It is optional, and we recommend it.
  • Add a webhook endpoint for Live mode. It is separate from your test endpoint and has its own signing secret.
  • Verify webhook signatures and reject old timestamps.
  • Send an Idempotency-Key on every POST /deliveries, book, cancel and wallet top-up.
  • Handle errors by HTTP status and error.code, never by message. Plan for INSUFFICIENT_BALANCE, QUOTE_EXPIRED and 429.
  • Fund your live wallet. See Wallet. (Platform accounts on invoicing: check credit.available on GET /wallet.)
  • Make one small live booking and follow it to delivered.

Next steps​