Guardant Health · OAuth Scopes

Guardant Health OAuth Scopes

OAuth 2.0 derived

Guardant Health 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://example.invalid/guardant-health/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.

HealthcarePrecision OncologyLiquid BiopsyGenomicsEMR Integration

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://example.invalid/guardant-health/oauth/token

Flows
clientCredentials

Scopes (0)

Guardant Health 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.

Guardant Health does not publish OAuth scopes; access is partner-provisioned during EMR onboarding (Epic Aura, Flatiron OncoEMR) with no public developer authentication documentation (https://guardanthealth.com/precision-oncology/for-institutional-partners/emr-integration-services/).

📄 Provider scope reference: https://guardanthealth.com/precision-oncology/for-institutional-partners/emr-integration-services/

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/guardant-health-openapi.yml
docs: https://guardanthealth.com/precision-oncology/for-institutional-partners/emr-integration-services/
note: Guardant Health does not publish OAuth scopes; access is partner-provisioned
  during EMR onboarding (Epic Aura, Flatiron OncoEMR) with no public developer
  authentication documentation (https://guardanthealth.com/precision-oncology/for-institutional-partners/emr-integration-services/).
schemes:
- name: partnerOAuth2
  source: openapi/guardant-health-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://example.invalid/guardant-health/oauth/token
  description: Placeholder. Partner-provisioned authentication is negotiated during EMR onboarding;
    no public auth flow is documented.
scopes: []