How is rate limitting done in your clients?

[toonsevrin]

Dear bol devs,

For my company, TCorp BV, I generated a go-client (source) from the openapi/swagger specification.

It appears that rate limiting is not part of the specification, and thus none of this information can be processed correctly by my generated client.

How did you deal with this over the various clients?

Also: bol.com's rate limiting is extremely low: Is it recommended that we write an indexing service (that indexes orders when they come in etc.) between bol.com and the rest of our internal services?

[toonsevrin]

EDIT: This is related to the actual retailer api, my apoligies. If you know the answers however, feel free to inform me!

[Niellles]

I've just realised that, unfortunately, there's nothing that handles rate limiting in this library. The response you get from the API has X-RateLimit-Remaining and X-RateLimit-Reset headers. See: https://tools.ietf.org/id/draft-polli-ratelimit-headers-00.html#rfc.section.3. I am planning on using these headers to handle rate limiting in my application.

As for your second question:

3.11. bol.com stelt de Limiet vast en is gerechtigd om de Limiet van tijd tot tijd aan te passen. Overschrijding van de Limiet kan resulteren in een (tijdelijke) blokkade van de toegang tot de Open- Api voor de betreffende Open API gebruiker. Het lokaal opslaan van de Content is, met inachtneming van het bepaalde in artikel 3.7, toegestaan.
~ Bol Open API Terms of Service