OAuth 2.1 overview
Vyde uses Authorization Code + PKCE. Your application sends the user to Vyde, the user decides what to share, and Vyde redirects back with a short-lived authorization code.
Environments
Section titled “Environments”| Service | Development | Production |
|---|---|---|
| Identity interface | https://identity.vyde.test:5173 |
https://identity.vyde.dev |
| API | https://api.vyde.test:8443 |
https://api.vyde.dev |
| Documentation | https://docs.vyde.test:5174 |
https://docs.vyde.dev |
Redirect URIs are environment-specific and must match exactly.
The flow
Section titled “The flow”- Register a public or confidential application.
- Generate
stateand a PKCE verifier in your application. - Redirect the browser to
/oauth2/authorize. - Verify
statein the callback. - Exchange the one-time code at
/oauth2/token. - Validate tokens before calling your API.
Scopes must be enabled for the application before they can be requested. An unenabled scope returns
invalid_scope, not a generic request error.