Rest API
mNo edit summary
mNo edit summary
Line 14: Line 14:
# User Information Query (KYC - Know-Your-Customer) Details
# User Information Query (KYC - Know-Your-Customer) Details
{{Edited|July|12|2024}}
{{Edited|July|12|2024}}
=== Authentication - POST ===
There are two credentials used in the open API
* Subscription Key
* API User and API Key for Oauth 2.0
The subscription key is used to give access to APIs in the API Manager portal. A user is assigned a subscription Key as and when the user subscribes to products in the API Manager Portal.
The API User and API Key are used to grant access to the wallet system in a specific country. API user and Key are wholly managed by the user through Partner Portal.
Users are allowed to generate/revoke API Keys through the Partner Portal.
However, on Sandbox Environment a Provisioning API is exposed to enable users to generate their own API User and API Key for testing purposes only.
[[File:Documentation Rest API 1733088545136.png|thumb|300x300px]]
[[File:Documentation Rest API 1733088844666.png|thumb|300x300px]]
=== Request-To-Pay  - POST ===
=== Transaction Status Inquiry - GET ===
=== Account Balance Inquiry - GET ===
=== Basic User Information Inquiry - GET ===
[[Category:Rest]]
[[Category:Rest]]

Revision as of 21:35, 1 December 2024

MDriven Turnkey can easily expose services via REST: Exposing Ourselves as a REST Service

You can also consume REST services from other systems: Rest Services In MDriven

The case below is about integrations with MOMO (Mobile Money) open APIs, show case show MDriven consuming RESTful APIs from an external system.

Here we see a UI of all the major services from the collections end points for MOMO API endpoints.

Documentation Rest API 1733087509985.png
  1. Authentication
  2. Request-To-Pay
  3. Transaction Status Inquiry
  4. Account Balance Inquiry
  5. User Information Query (KYC - Know-Your-Customer) Details


Authentication - POST

There are two credentials used in the open API

  • Subscription Key
  • API User and API Key for Oauth 2.0

The subscription key is used to give access to APIs in the API Manager portal. A user is assigned a subscription Key as and when the user subscribes to products in the API Manager Portal.

The API User and API Key are used to grant access to the wallet system in a specific country. API user and Key are wholly managed by the user through Partner Portal.

Users are allowed to generate/revoke API Keys through the Partner Portal.

However, on Sandbox Environment a Provisioning API is exposed to enable users to generate their own API User and API Key for testing purposes only.

Documentation Rest API 1733088545136.png
Documentation Rest API 1733088844666.png

Request-To-Pay - POST

Transaction Status Inquiry - GET

Account Balance Inquiry - GET

Basic User Information Inquiry - GET

This page was edited 58 days ago on 01/20/2025. What links here