Digitail · OAuth Scopes
Digitail OAuth Scopes
OAuth 2.0
derived
Digitail 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://vet.digitail.io/oauth/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.
VeterinaryPIMSPractice ManagementPetsHealthcareSchedulingBillingSoftware-as-a-Service
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://vet.digitail.io/oauth/authorize
https://vet.digitail.io/oauth/authorize
Token URL
https://vet.digitail.io/oauth/token
https://vet.digitail.io/oauth/token
Flows
authorizationCode
authorizationCode
Scopes (0)
Digitail 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.
Digitail's OAuth 2.0 authorization-code-with-PKCE flow does not use or document any scopes; access is granted per approved application registration (https://documentation.digitail.io/authentication).
Digitail's OAuth 2.0 authorization-code-with-PKCE flow does not use or document any scopes; access is granted per approved application registration (https://documentation.digitail.io/authentication).
📄 Provider scope reference: https://documentation.digitail.io/authentication
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.