Runtime error because Ynab API servers discontinued sending X-Rate-Limit header #37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… 2023 (ynab/ynab-sdk-js#164) which now breaks the client ("invalid rate limit string"). There's no way to obtain the current rate limit via the API (https://api.ynab.com/#rate-limiting), so it's probably best to rip out all related functions. This will break anyone relying on the public RateLimit() function, but their applications are already broken throwing runtime errors because of the missing header.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ynab API servers discontinued sending the X-Rate-Limit header in late 2023 (ynab/ynab-sdk-js#164) which now breaks the client ("invalid rate limit string") at runtime. There's no way to obtain the current rate limit via the API (https://api.ynab.com/#rate-limiting), so it's probably best to rip out all related functions. This will break anyone relying on the public RateLimit() function, but their applications are already broken throwing runtime errors because of the missing header.
As a side note, the client used to work for me until about a month ago and then suddenly broke, so I suspect the API servers included the X-Rate-Limit header until recently and then turned it off (early 2025).