You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: