Weave · OAuth Scopes
Weave OAuth Scopes
OAuth 2.0
derived
Weave uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
Tokens are issued from https://auth.weaveconnect.com/oauth2/default/v1/token.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CommunicationHealthcareVoIPMessagingSMSSchedulingPaymentsReviewsDentalVeterinary
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://auth.weaveconnect.com/oauth2/default/v1/authorize
https://auth.weaveconnect.com/oauth2/default/v1/authorize
Token URL
https://auth.weaveconnect.com/oauth2/default/v1/token
https://auth.weaveconnect.com/oauth2/default/v1/token
Flows
authorizationCode
authorizationCode
Scopes (0)
Weave implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
Weave does not publish API-permission OAuth scopes - the developer portal (https://dp.getweave.com) is behind a login, and the live OIDC discovery document at https://oidc.weaveconnect.com/.well-known/openid-configuration lists only the standard OIDC scopes openid, offline, and offline_access, with access governed by the developer application rather than granular scopes.
Weave does not publish API-permission OAuth scopes - the developer portal (https://dp.getweave.com) is behind a login, and the live OIDC discovery document at https://oidc.weaveconnect.com/.well-known/openid-configuration lists only the standard OIDC scopes openid, offline, and offline_access, with access governed by the developer application rather than granular scopes.
📄 Provider scope reference: https://oidc.weaveconnect.com/.well-known/openid-configuration