Skip to main content
Question

MTN MoMo Sandbox endpoints returning HTTP 500

  • July 14, 2026
  • 8 replies
  • 116 views
S

The Sandbox Collection token/payment flow and Sandbox User Provisioning endpoint are returning HTTP 500 Internal Server Error.

I tested both the Primary and Secondary Collection subscription keys, but received the same result.

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

Activity IDs:
e8bd5c96-1955-4c73-9b47-285372a833f0
c7d94c70-d94b-419f-81f3-1b3f9606a18e
903d8124-fc15-4129-9c88-a47d8c410224

Please confirm whether the sandbox services are currently operational and advise when they will be restored.

    8 replies

    S
    • sambongoza
    • Author
    • New Member
    • July 14, 2026

    Additional context: this Collections sandbox integration had been working for approximately six months using the same credentials. The subscription still shows as Active.

    I have now tested the provisioning endpoint directly with both the Primary and Secondary Collection subscription keys, but both return HTTP 500.

    Has anyone experienced this recently? If so:

    • Did it resolve automatically when the sandbox came back online?

    • Did you have to create a new API User/API Key?

    • Is anyone currently able to create an API user or obtain a Collection access token?

    Please do not share any credentials. Even a confirmation that others are experiencing the same problem would be helpful.

    K
    • kpatchavi
    • New Member
    • July 14, 2026

    Same here

    B
    • Brun-Art
    • New Member
    • July 14, 2026

    I have the same issue

    J
    • josephmbuzi
    • New Member
    • July 14, 2026

    Am having the same issue also

    E
    • elcidrealm
    • New Member
    • July 14, 2026

    I have same issue

     

    S
    • sambongoza
    • Author
    • New Member
    • July 15, 2026

    has anyone had this issue resolved yet?

     

    J
    • josephmbuzi
    • New Member
    • July 15, 2026

    has anyone had this issue resolved yet?

     

    Not yet

    S
    • sharpdev
    • New Member
    • July 21, 2026

    Additional context: this Collections sandbox integration had been working for approximately six months using the same credentials. The subscription still shows as Active.

    I have now tested the provisioning endpoint directly with both the Primary and Secondary Collection subscription keys, but both return HTTP 500.

    Has anyone experienced this recently? If so:

    • Did it resolve automatically when the sandbox came back online?

    • Did you have to create a new API User/API Key?

    • Is anyone currently able to create an API user or obtain a Collection access token?

    Please do not share any credentials. Even a confirmation that others are experiencing the same problem would be helpful.

    Hey sambongoza,

    If you’re using Postman:

    • Put these in “Headers”:
      • X-Reference-Id: <your-uuid>
      • Ocp-Apim-Subscription-Key: <your-subscription-key>
      • Content-Type: application/json
    • Put this in “Body” (choose Raw the JSON language). Note that subdomains are not working for this:
      • {"providerCallbackHost": "your-callback-url"}
    • Request URL should be as you set it: https://sandbox.momodeveloper.mtn.com/v1_0/apiuser

    Send the request and you should have a 201 Created response.

    Terms & ConditionsAccessibility statement