Skip to content
English
Customer portal
Go to reloadly.com
  • There are no suggestions because the search field is empty.

Preferred platforms for integrating our API

Start Here

Preferred platforms for integrating our API

Learn about the best practices we recommend regarding integration environments and architectures.

Estimated time

5 minutes

Level

Intermediate

You'll need

A Reloadly developer account

Reloadly APIs are primarily built to support a B2B business model. As a B2B customer, you'll typically integrate Reloadly APIs into an existing business application, and the right integration path depends on your delivery channel and your system architecture.

It starts with your delivery channel

The right way to integrate with Reloadly depends on how you deliver your services to your end users — for example, through mobile apps, browser-based apps, headless APIs, or some form of SDK — and on your overall system architecture.

 
 
 
$
📡

Mobile apps connecting to Reloadly's services (top-up, gift cards)

Mobile apps without a backend

Consider a mobile app delivery channel where airtime and Digital Gift Cards are being sold, and you don't intend to have backend APIs for your mobile app. In that case, our SDKs — either iOS or Java (for Android) — will be the easiest integration path for you.

💡 Tip: Going SDK-first on mobile means you don't need to stand up or maintain your own backend just to call Reloadly.

Browser-based and web apps

Another common scenario is delivering your services and products through browser-based websites. Choose the integration path that matches your needs:

  • Reloadly widget — the easiest option; requires no SDK and minimal setup.
  • SDK integration — use this when you need greater control over the user experience.
  • NodeJS SDK — the recommended choice if your web app is built with a modern SPA framework like Angular or React.

 
 
 
 
 
 
 
 

Backend and server-side integrations

Based on your application architecture, you can choose to manage calls to Reloadly from your front end, or route the requests through your own backend.

When integrating with Reloadly from backend runtimes — for example, a Java Spring Boot app, a .NET backend, or a Go backend — you'll again use the relevant SDK for your programming language. Reloadly offers dedicated SDKs for Java, NodeJS, .NET, and Go backend environments. This is the recommended approach in most cases.

ℹ️ No single right answer: There's no single preferred way to integrate with Reloadly. It depends on your technology landscape, use case, and application architecture — which is why we offer multiple integration paths and flexible SDKs.

Calling the REST API directly

While it's possible to consume our API endpoints directly with raw HTTP calls, we generally discourage this. It's significantly more work than using an SDK, and it requires you to manage security requirements, tokens, and token expiry handling yourself. This route gives you the most flexibility, but it's the least preferred approach.

Important: If you do choose this path, you are fully responsible for all authentication and token lifecycle management. No SDK safeguards are in place.

❓ Frequently asked questions

Which SDKs does Reloadly offer?

Reloadly offers SDKs for iOS, Java (Android and backend), NodeJS, .NET, and Go, so you can pick the one that matches your stack. You can find links to each SDK in the Reloadly developer documentation.

Do I have to use an SDK?

No, you can call the REST API directly. However, we recommend using an SDK in most cases, since it handles authentication, token refresh, and other security details for you.

What if my app doesn't fit neatly into one of these scenarios?

These are common patterns, not strict rules. Many businesses mix approaches — for example, using the widget for a simple web flow while using an SDK on the backend for other parts of the integration.

Still having trouble?

Our support team is here to help.

Contact support →