Swagger - number of requests exceeded

[Florian Haase]

Hi,

now the Swagger reports all the time that the hourly number of requests is exceeded. That means that we don't get the "try it out" to work again. (we have not sent any requests today by the swagger before) 

I had the same problem already yesterday with another user.

Regards,

Florian

[Yıldırım]

Hello, 

As of today, swagger-ui is shared with all developers, so you might get throttled even though you did not make any request due to the total of the transactions might have been reached out the threshold.

We're currently working on a new approach to bend this rule with Request / Per Company. We will keep the community posted with future developments.

[Florian Haase]

Hi

we are using the swagger a lot for testing of single calls and investigation of possibilities and solutions. For this purpose it would be great to have it accessible. We on development can use postman to try calls, but for the consultants its easier with the swagger.

But thank you for the quick answer.

Florian

[Yıldırım · Accepted solution]

Thank you too Florian ! We definitely understand that using swagger can be easier for the consultants. If this is  mostly required for testing of single calls and investigation / documentation etc,  We'd also recommend that considering the option of generating a token with your Test Client ID via Postman and storing it in the postman instances between your consultants. This would be also a concrete solution, if you'd like to see the guideline, it can be found here : Generating token with oAuth2 for Visma.Net API in Postman