In our Dashboard we can configure the different options of our technical API. In the section profile we can configure webhook, number of retries, endpoint for the iframe, etc.
We will describe this information in more detail below.
2. Development Environment
Mobadoo uses two environments for managing the integration process: Stage y Producción. The APIs’ URLs are the following:
- Websocket: wss://api-stage.mobadoo.com/
- Endpoint URL: https://api-stage.mobadoo.com/api/v1/
- Token: Test_key
- Online URL: https://online-stage.mobadoo.com/?hash=XXXX&client_id=XXXX&profile=XXXX
- Websocket: wss://api.mobadoo.com/
- Endpoint URL: https://api.mobadoo.com/api/v1/
- Token: Test_key
- Online URL: https://online.mobadoo.com/?hash=XXXX&client_id=XXXX&profile=XXXX
To make all the configurations of the Mobadoo API management, we will go to the profile section in the Mobadoo Dashboard
The session TOKEN for the APIs could be found at the Mobadoo’s back-office console, in the profile section, as it is shown on the following image:
Clicking in the user name at the upper-right corner, highlighted in yellow, takes you to the account’s detailed information and configuration.
Clicking on the “eye” icon, it is possible to see it. It is also possible to copy it, clicking on the copy icon. The token allows you to place API calls as your user.
2.3 Token expiration
Even though the token does not expire, it could be refreshed from the back-office console.
Mobadoo has designed a service in its system so that the customer does not have the need to be making constant calls.
Mobadoo with the webhook service will keep the client informed at all times about changes in product information from the ODDS.
We can configure the URL of the webhook in the Dashboard profile, as shown in the image. We can also configure the retry of calls if necessary, by default its set of 3 retries
4. Iframe URL
In this section we can configure the iframe url where Mobadoo will make the calls to generate the tickets and request the user’s credit