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

⬆ Support v5 of the RTE API #69

Merged
merged 1 commit into from
Nov 11, 2023
Merged

⬆ Support v5 of the RTE API #69

merged 1 commit into from
Nov 11, 2023

Conversation

kamaradclimber
Copy link
Owner

@kamaradclimber kamaradclimber commented Nov 11, 2023

We try v5 first and fallback to v4 if we receive a 403. There is apparently no way to know if an api key has been generated for v5 or v4 but they are incompatible. Only way to know is to test at runtime.

Fix #68
Fix #67

We try v5 first and fallback to v4 if we receive a 403.
There is apparently no way to know if an api key has been generated for
v5 or v4 but they are incompatible. Only way to know is to test.

Fix #68
Fix #67
@kamaradclimber kamaradclimber merged commit caa957f into main Nov 11, 2023
@kamaradclimber kamaradclimber deleted the fix68 branch November 11, 2023 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support api v5 Plus rien ne remonte
1 participant