# Getting Started ## Steps on creating your first API Request 1. Fork the Collection 2. Create Subscription Keys 3. Create API User and API Key 4. Get Access Token 5. Make Your fisrt MoMo API Call ## Step 1: Fork the collection using Run In Postman [<img src="https://run.pstmn.io/button.svg" alt="Run in Postman">](https://app.getpostman.com/run-collection/28452721-0df6ecfa-f9a4-41ed-8e1e-7581097d1c4e?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D28452721-0df6ecfa-f9a4-41ed-8e1e-7581097d1c4e%26entityType%3Dcollection%26workspaceId%3D66fe3943-b010-4047-ad82-618785225cc8) ## Step 2: Create Subscription Keys 1. Sign up [https://momodeveloper.mtn.com](https://momodeveloper.mtn.com) 2. Navigate to the products page [Product-descriptions](https://momodeveloper.mtn.com/Product-descriptions). 3. Select drop down on product that suits the business case and subscribe. 4. After completion, you can locate the Subscription Keys in [your profile](https://momodeveloper.mtn.com/profile). Access additional information through the link below on creating subscription keys [How to create subscription keys on MoMoDeveloper | MoMo Dev Community (mtn.com)](https://momodevelopercommunity.mtn.com/how-to-59/how-to-create-subscription-keys-on-momodeveloper-148) 5. Navigate to the Variables and update as mapped below | **Subscription name** | **Key Type** | **Variable** | | --- | --- | --- | | Disbursements | Primary | `Disbursement_Subscription-Key` | | Collections | Primary | `Collection_Subscription-Key` | #### **NOTE: Use the Primary Key** ## Step 3: Generate API user and API Key 1. Fork the SandBox Provisioning Collection using run in Postman [<img src="https://run.pstmn.io/button.svg" alt="Run in Postman">](https://app.getpostman.com/run-collection/28452721-83d6c7e7-0135-4b37-94fe-2cbef87b7859?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D28452721-83d6c7e7-0135-4b37-94fe-2cbef87b7859%26entityType%3Dcollection%26workspaceId%3D66fe3943-b010-4047-ad82-618785225cc8) 2. Run the _**SandBox Provisioning Collection**_ , copy the `api user` and `api key` displayed via the console and test results. 3. Navigate to the Variables of the _**MoMo Open APIs Collection**_ and modify api_user and api_key respectively ## Step 4: Get Access Token An access token is automatically generated using a default `api_user` and `api_key`. MoMo recommends using your own api_user and api_key from **Step 3** by entering the values under the **Variables** tab. A pre-request script will generate and manage expiry of the `access_token` automatically. > **Recommended to generate a new Access Token only after expiry of the Old one and****not a new token for every request** ## Step 5: Make Your first MoMo API Call 1. In your workspace, navigate to your fork of the MoMo Open APIs collection. 2. Select **Get Paid** > **Request Payment** 3. Select the **Send** button to request a payment. On a successful call, the API returns a 202 Accepted response code 4. .Customer will receive a PIN to approve the debit from their MoMo Wallet. 5. Check configured Callback URl for status of the Request. 6. Request Status can be generated under Select **Get Paid** > **Payment Status** 7. Select the **Send** button to request a payment. On a successful call, the API returns a 200 OK Accepted response code, with Status of the request in the response body #### **Test MSISDN** Change the value for the Collection Variable MSISDN to produce the responses below. Test Results with the different responses will be expected for go live submissions | **Number** | **Response** | | --- | --- | | 46733123450 | Failed | | 46733123451 | Rejected | | 46733123452 | Timeout | | 56733123453 | Success | | 46733123454 | Pending | X-Refrence-Ids are auto generated UUID version Strings and these are interpretended as request_ids. They are saved in the request Ids variables. ## Golive With the Test Results It is anticipated that you will provide the Test Results derived from the MoMo Open APIs collection. The Results must demonstrate your understanding of the API Flow and Syntax, and the testing of various sample responsesfor the APIs you plan to use.

Versori has established itself as the third generation of Integration Platform as a Service (iPaaS). Versori builds custom integrations for its customers using an intuitive visual user interface.

Versori’s connector engine means there is no dependency on an existing library of apps, all you need to start is the documentation of the app or system you want to integrate to.