MoMo API Upgrade - One API
The MoMo API Platform is being enhanced to strengthen security, standardisation, monitoring, and operational efficiency. As part of these improvements, three mandatory implementation changes are being introduced, which all partners must implement, validate, and complete within the prescribed timelines.
- Credential Migration (New User ID & Credential Token)
- Token Generation Changes (Mandatory X-Target-Environment Header)
- Base URL Changes
These are the primary areas that should be validated during partner readiness.
Key Message for Partners
The MoMo API platform enhancement requires partners to update their base URL from https://proxy.momoapi.mtn.com or https://ericssonbasicapi1.azure-api.net to the new MoMo API base URL: https://momoapi.momo.africa.
API endpoints, business functionality, request payloads, and response structures remain unchanged.
Partners are also required to update their credentials by:
- Replacing the API User with the UserID.
- Replacing the API Key with the Credential Token.
Additionally, partners must review their Access Token generation requests and ensure that the now-mandatory X-Target-Environment header is included.
Follow Guide below to generate your new set of credentials.
Guide for Generating UserId and Credential Token
Credential Update
What changes
Partners must replace the existing API User and API Key used for token generation with new credentials generated from the Partner Portal. Link for the country specific Partner Portal can be attained by reaching to your account manager or relationship manager:
- User ID (Identity)
- Credential Token (Password)
After migration, the existing API User/API Key credentials will no longer be valid for authentication on the new platform.
Before upgrade
Partner uses:
API User = 12345678-abcd
API Key = abcxyz987654
Authentication:
base64(API_USER:API_KEY)
Example:
Authorization: Basic base64(12345678-abcd:abcxyz987654)
After upgrade
Partner generates new credentials from the Partner Portal:
User ID = user_12345
Credential Token = token_987654321
Authentication:
base64(USER_ID:CREDENTIAL_TOKEN)
Example:
Authorization: Basic base64(user_12345:token_987654321)
Token Generation Changes
What changes
The Create Access Token endpoint remains the same, but the authentication details and required headers change as follows:
| Component | Before | After |
| Authorization Secret | API Key | Credential Token |
| X-Target-Environment | Optional | Mandatory |
| Subscription Key | Required | No Change |
Before upgrade
POST /collection/token
Authorization: Basic base64(API_USER:API_KEY)
Ocp-Apim-Subscription-Key: SUBSCRIPTION_KEY
Example:
POST https://proxy.momoapi.mtn.com/collection/token
Authorization: Basic base64(12345678-abcd:abcxyz987654)
Ocp-Apim-Subscription-Key: 123456789
After upgrade
POST /collection/token
Authorization: Basic base64(USER_ID:CREDENTIAL_TOKEN)
Ocp-Apim-Subscription-Key: SUBSCRIPTION_KEY
X-Target-Environment: mtnuganda
Example:
POST https://momoapi.momo.africa/collection/token
Authorization: Basic base64(user_12345:token_987654321)
Ocp-Apim-Subscription-Key: 123456789
X-Target-Environment: mtnuganda
NOTE: The X-Target-Environment, is currently being passed in other API calls and is country specific. Please maintain the same value you are using for the other API calls e.g mtnuganda, mtnghana, mtncameroon etc
Base URL Changes
What changes
Partners must update the base URL used for all API requests as part of the migration to the new MoMo API environment.
✅ API endpoints remain unchanged.
✅ Request and response payloads remain unchanged.
✅ Only the hostname/base URL changes.
Before upgrade : MoMo API
All integrations point to:
https://proxy.momoapi.mtn.com or https://ericssonbasicapi1.azure-api.net
Examples:
POST https://proxy.momoapi.mtn.com/collection/token
POST https://proxy.momoapi.mtn.com/collection/v1_0/requesttopay
GET https://proxy.momoapi.mtn.com/collection/v1_0/requesttopay/{referenceId}
After upgrade: New MoMo API environment
All integrations must be updated to:
Examples:
POST https://momoapi.momo.africa/collection/token
POST https://momoapi.momo.africa/collection/v1_0/requesttopay
GET https://momoapi.momo.africa/collection/v1_0/requesttopay/{referenceId}
Before vs after comparison
| Component | Before | After |
| Base URL | https://proxy.momoapi.mtn.com | https://momoapi.momo.africa |
| /collection/token | https://proxy.momoapi.mtn.com/collection/token | https://momoapi.momo.africa/collection/token |
| /collection/v1_0/requesttopay | https://proxy.momoapi.mtn.com/collection/v1_0/requesttopay | https://momoapi.momo.africa/collection/v1_0/requesttopay |
| API Payloads | No Change | No Change |
| API Headers | Updated as per migration requirements | Updated as per migration requirements |
| Business Functionality | No Change | No Change |
Example upgrade configuration
Current Configuration
{
"baseUrl": "https://proxy.momoapi.mtn.com"
}
New Configuration
{
"baseUrl": "https://momoapi.momo.africa"
}
Country/OPCO Migration Status
| Country | Live on new Platform |
|---|---|
| Congo Brazzaville | Live |
| Liberia | Live |
| Uganda | Live |
| Eswatini | Live |
| Ivory Coast | Live |
| Benin | Live |
| Cameroon | InProgres |
| Ghana | InProgres |
| Zambia | InProgres |
| South Africa | InProgres |
| Rwanda | InProgres |
| Nigeria | InProgres |
| South Sudan | InProgres |
NOTE: For OPCOs/Countries inProgress, please reach out to your OPCO Account Manager for confirmation on GoLive Date.
Support Channels
Partners can use the following channels for support, technical guidance, and community-based learning during the transition to the new MoMo API platform.
- Email support: Send queries, migration issues, and technical support requests to support.momodeveloper@mtn.com.
- Developer community: Ask questions and access discussions, guidance, and shared partner resources through the MoMo Developer Community.