Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRANSIP: Should re-try when rate-limited #3371

Open
tlimoncelli opened this issue Jan 15, 2025 · 1 comment · May be fixed by #3378
Open

TRANSIP: Should re-try when rate-limited #3371

tlimoncelli opened this issue Jan 15, 2025 · 1 comment · May be fixed by #3378

Comments

@tlimoncelli
Copy link
Contributor

Describe the bug
The good news: TRANSIP is faster.
The bad news: We're now getting "you're going too fast" messages

To Reproduce
n/a

Expected behavior
n/a

DNS Provider

  • TRANSIP

Additional context
n/a

CC blackshadev @cafferata

@cafferata
Copy link
Collaborator

Rate limit
The rate limit for this API uses a sliding window of 15 minutes. Within this window, a maximum of 1000 requests can be made per user.

Every request returns the following headers, indicating the number of requests made within this window, the amount of requests remaining and the reset timestamp.

X-Rate-Limit-Limit: 1000
X-Rate-Limit-Remaining: 650
X-Rate-Limit-Reset: 1485875578

When this rate limit is exceeded, the response contains an error with HTTP status code: 429: Too many requests.

https://api.transip.nl/rest/docs.html#header-rate-limit

@tlimoncelli tlimoncelli linked a pull request Jan 15, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants