Closed adriens closed 6 years ago
Une fois partagé, on peut même monitorer les perfs du ws 😆
C'est trop de la balle @mbarre !!!
In postman, to tempalte the url, https://www.getpostman.com/docs/postman/sending_api_requests/requests
we have to use the following pattern :
https://ticketresto-nc-rest.herokuapp.com/accounts/:identifier/:password/balance
After that, in fact, before, variables should be stored on top of the collection sot API calls inherit from that.
Once var globally set (at the collection leve), the api call url is the following one :
https://ticketresto-nc-rest.herokuapp.com/accounts/{{identifier}}/{{password}}/balance
Ticket resto Collection set up ! Still have to get a look on how not ot share the keys, but i'mq uite confident that it should be feasible as this feature is usually used to provide API Key 😸
First ever live Postman API for ticket resto : https://documenter.getpostman.com/view/3489712/ticket-resto/7LuYy9B
It's a default generation than can be custmozed. The actual one is the one generated only by clicking "Next"
Test on the service collection :
we can see the service wakeup on the first call, the getting a standard response time on the second call :
To share the POSTMAN request (to make integrations easier for others), it would be conveniet to put auth parametrized. For now, i'm using the "No Auth" and it works...but i could not share it to Postman (https://www.getpostman.com/docs/postman/team_library/sharing)