Skip to main content
Question

Sandbox Collections API User provisioning returns HTTP 400

  • August 13, 2026
  • 0 replies
  • 5 views

Hello MTN MoMo Support/Community,

I am integrating the MTN MoMo Collections API for my application, Glowza.

I have an active Sandbox subscription:

Product: Collections
Subscription: FakorBorla Sandbox
Environment: Sandbox

I am trying to provision an API User using the Sandbox User Provisioning API.

Endpoint:

POST https://sandbox.momodeveloper.mtn.com/v1_0/apiuser

Request headers:

X-Reference-Id: [fresh UUID v4]
Content-Type: application/json
Ocp-Apim-Subscription-Key: [Collections Primary Subscription Key]

Request body:

{
  "providerCallbackHost": "webhook.site"
}

The request consistently returns:

HTTP/1.1 400 Bad Request

Content-Length: 0

There is no response body explaining the error.

I have also tried the GET API User endpoint with the same UUID:

GET /v1_0/apiuser/{X-Reference-Id}

This also returns:

HTTP/1.1 400 Bad Request

I have verified that:

- The subscription is active.
- The subscription product is Collections.
- I am using the Collections Primary Subscription Key.
- The subscription key is 32 characters.
- The X-Reference-Id is a valid UUID v4.
- The request is being sent to the Sandbox environment.
- The request body follows the documented providerCallbackHost format.
- The Sandbox User Provisioning API is returning 400 with an empty response.

Could you please check whether there is an issue with API User provisioning for my Sandbox Collections subscription, or whether the subscription/API-user provisioning service needs to be reset or enabled on your side?

Thank you.