Skip to main content
Connecting uses the OAuth 2.0 authorization-code grant. Confidential clients authenticate with a client_secret; public clients (SPAs / mobile) use PKCE.

1. Send the user to authorize

Redirect the user’s browser to the authorize endpoint:
Hyperwisor shows a login + consent screen. On approval, the user is redirected back to your redirect_uri with a one-time code:
The redirect_uri must exactly match one registered for your client_id, and every requested scope must be in your allowed set — otherwise the request is rejected. Always verify state matches what you sent.

2. Exchange the code for a token

Your backend exchanges the code (JSON or form-encoded):
For public clients, omit client_secret and send code_verifier instead:
Response:
The code is single-use and expires in 5 minutes. Store the tokens against the partner user (never in a browser for confidential clients).

3. Call the Partner API

Send the access token as a Bearer header:
See Create Products.

Refreshing

Access tokens live 1 hour. Refresh (rotates both tokens):
The first time a user approves a manufacturer:* scope, their Hyperwisor account is provisioned as a manufacturer. Existing accounts are upgraded, not duplicated.