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

API key w/ proprietary signature or OAuth2 with bearer token #129

Open
KampfCaspar opened this issue Mar 27, 2024 · 0 comments
Open

API key w/ proprietary signature or OAuth2 with bearer token #129

KampfCaspar opened this issue Mar 27, 2024 · 0 comments

Comments

@KampfCaspar
Copy link

Sorry but I don't really understand if there are two different API conventions at OVH:

The documentation and 'old' api console seem to use API keys restrained by method and path. These repositories are needed because api calls are 'signed' with a proprietary algorithm.

The 'preview' console however, shows examples using plain curl calls with a 'Bearer' Token in JWT format. There are beta api calls for clients, however no documented api calls for the oauth2 flow (might go over the main ovh.com flow?).

Now, can I 'just' use REST with OAuth2 - or is the use of the proprietary pseudo-REST calls the official way?

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

No branches or pull requests

1 participant