Uncover, learn and Enlighten

Members the 400 bad request response without descriptions is unprofessional. if the request body is wrong then an appropriate response code should be returned by the api endpoint. this makes it easier for software developers to guide themselves. for 7 years av been on this API and i still wonder why nothing has changed. Eg when creating an invoice am glad this {    "message": "Currency not supported.",    "code": "INVALID_CURRENCY"} comes but then beyond that its BAD request without any meaningful response code 

  Can I get guidance on building my first integration?What resources are best for beginners?Are there opportunities for non-developers to contribute ideas?  

hey community what is the business model of a website exactly.

Tokens should be refreshed 10 Minutes prior to expiry. A token expires after 60 minutes and it is recommended that it is refreshed 10 minutes prior to expiry. Do not create a token for every transaction. When configuring a Call Back URL, ensure that you use a Trusted Immediate Root CA   https://momodeveloper.mtn.com/api-documentation/callback/.In a Scenario where CA is not listed, please contact the Account Manager Ensure that you advise your Account Manager a month prior to changing your Root CA – failure to notify will inadvertently result in a failure of all transactions. When a call back is not received, please check status of the transaction(Get Status API ) 5 Minutes after the transaction was initiated.Before crediting or debiting an account, check the account validity and confirm ownership. Get status transaction requests are capped to 10 requests per second. Keep within the threshold to avoid rate limit error.

 Before proceeding, ensure you peruse this guide if there's a function you desire that's currently unavailable, or if you wish to share your thoughts about the system's operation, you have the option to propose a concept. Develop a ConceptIf you're unable to locate a pre-existing Concept or Discussion related to your topic, opt for 'Develop a concept' on the Concepts homepage.The Perfect Concept Layout:Heading: Your Concept's overarching goal.Explanation: The particulars should unambiguously outline your demands. Be sure to encompass:A distinctly articulated use case or business issue that isn't satisfied with the existing features. For improvement suggestions, offer comprehensive specifications for the function you're pursuing. You're free to insert hyperlinks to associated concepts/documents to demonstrate why the present features don't cater to your needs. Be thorough, depict if possible, to reveal all the elements. Confirm that you're utilizing all the Product sector/module labels