Reloadly provides infrastructure for connecting to the mobile digital economy.
By leveraging Reloadly's services you can purchase Mobile Airtime, Gift Cards and pay utilities.
With a presence for mobile airtime payments in over 140 countries, our products apply to various use cases such as
  • Airtime remittances
  • Airtime gifting (single and recurrent)
  • Subscription bundles
  • Transaction history and data
  • Information on promotions
  • Information on subscription discounts
Before going into the details, there are a few concepts you need to be familiar with.
First of all, let's do a quick recap of how Reloadly works:
Every Reloadly account has a wallet. Every time a Reloadly user makes a purchase, the price is deducted from this wallet so, in order for your operations to be succesful, you need to make sure the wallet has enough money to cover for the requested transaction.
So, before making any purchase, you need to recharge your wallet.
Assuming you have enough credit, you can start making requests to Reloadly's servers.
Our APIs are built around the concept of RESTful, which means you'll be making simple HTTP requests to specific URLs (endpoints) depending on what you're trying to accomplish.
In general, a request to a Reloadly endpoint will look like this:
Service can be one of:
  • topups
  • giftcards
  • utilities
For instance, if you wanted to make an airtime topup you'd issue a request to https://topups.reloadly.com/topups and, if you want to get a list of all the supported mobile operators you'd be making a request to https://topups.reloadly.com/operators.
Each service has its own set of resources which are defined according to its bussiness case. That's why you won't find an endpoint like https://giftcards.reloadly.com/topups or https://topups.reloadly.com/redeem-instructions
In order to keep our users safe our APIs rely on OAuth 2.0. This means, before a request can be accepted, you'll need to get a token.
It's important to know that a token is only valid for one service. If you need to interact with different services you'll need one token for each.
Finally, another key aspect of Reloadly development is the notion of environment.
Reloadly offers two operational environments:
  1. 1.
  2. 2.
There are three main differences between Production and Sandbox:
  1. 1.
    The endpoint prefix (https://<service>.reloadly.com and https://<service>-sandbox.reloadly.com respectively)
  2. 2.
    How your wallet is left after a succesful operation
  3. 3.
    What do your recipients get
The production environment is the actual live one. This means that transactions made here are for real: when a transaction is succesful your wallet will be charged and the recipient will get the good you paid for.
The sandbox environment is meant to be used for testing purposes. It will act exactly like the production environment in terms of how requests are interpreted and responses are generated but it will not deduct any credit from your wallet, nor will recipients of your purchases receive anything.
In order to keep you from mistakingly making requests to production when you actually wanted to make test requests, tokens will also be restricted by environment.
This means you'll need to get a token for each specific service and environment you want to use.
Now that you have a clear understading of the general concepts you're ready to go into the specifics of the service you'll be using for your application:
Go here for a Airtime topups, here for giftcards and here for utility bill payments.
Last modified 1mo ago
Copy link