Pagination and SameRequestLimit

[Anonymous]

When requesting a range of data items (customers etc.) using pagination, does the "SameRequestLimit" take the requested page into consideration? When trying this out in the swagger ui, we get error 429 (SameRequestLimit) when requesting more than five different pages within one minute. Is that the intended behaviour?

[SierdW]

Any updates in this item? We are considering a new integration which needs to consume a lot of data from eg the journaltransaction endpoint. Will requests which have different pagenumbers be considered as samerequest, or better: when is a request considered as the same request?

[Magnus Johnsen]

Hi,

This should not be an issue for anyone, this is only regarding the Swagger UI.

When testing the API we recommend using a client like Postman/Fiddler or cURL with your own token.

By doing this, you will not encounter this rate limit. 

[Magnus Johnsen]

Hi,

We're looking into if this is how it was intended, we can confirm that it does happen and can agree that sending different parameters should in most cases be considered different requests. 

Our recommendation in general though is to test these types of cases in an API testing application like Postman/Fiddler.