[Feature]: Respect Paddle rate limit

[Bre77]

Tell us about your feature request

The Paddle SDK doesnt respect the Paddle API rate limit, and doesnt provide the developer the means to respect the Paddle API rate limit.

Given this is an async library, requests that would hit the rate limit should automatically wait an appropriate amount of time before returning, or at least retry after the Retry-After header time. This doesnt have to be default behavior, but should be an option.

Worst case, provide the header values back via the SDK so the application can handle these themself. The current error does not include the value of the Retry-After header, so its unclear how long to wait until retrying.

What problem are you looking to solve?

I dont want to have to think about the Paddle API rate limit when using the SDK, because this should be handled for me. Alternatively I want the SDK to provide me appropriate information so that I can manage the rate limit myself.

Additional context

  type: 'api_error',
  code: 'too_many_requests',
  detail: 'You have exceeded the allowed rate limit, please retry your request after the number of seconds in the Retry-After header.',
  documentationUrl: 'https://developer.paddle.com/errors/shared/too_many_requests',
  errors: null

How important is this suggestion to you?

Important

[vifer]

Hi @Bre77 ,
Thank you for your detailed feedback! Handling API rate limits more effectively in the SDK is definitely something we want to support and we’ll explore it for future updates.

We appreciate your contribution, please feel free to share any further ideas!