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 ManagementPetsHealthcareSchedulingBillingSaaS

Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://vet.digitail.io/oauth/authorize

Token URL
https://vet.digitail.io/oauth/token

Flows
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).

📄 Provider scope reference: https://documentation.digitail.io/authentication

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/digitail-openapi.yml
docs: https://documentation.digitail.io/authentication
note: 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).
schemes:
- name: oauth2
  source: openapi/digitail-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://vet.digitail.io/oauth/authorize
    tokenUrl: https://vet.digitail.io/oauth/token
  description: OAuth 2.0 authorization-code grant with PKCE. Bearer access token is long-lived;
    a refresh token is also returned.
scopes: []