Everly Health · OAuth Scopes

Everly Health OAuth Scopes

OAuth 2.0 searched

Everly Health publishes 2 OAuth 2.0 scopes via the authorizationCode and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Everly Health API on a user’s behalf.

Tokens are issued from https://secure.everlywell.com/oauth2/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.

CompanyHealthHealthcareDigital HealthDiagnosticsLab TestingTelehealthConsumer HealthIdentity

Scopes: 2 Flows: authorizationCode, password Method: searched

OAuth endpoints

Authorization URL
https://secure.everlywell.com/oauth2/authorize

Token URL
https://secure.everlywell.com/oauth2/token

Flows
authorizationCodepassword

Scopes (2)

Scope	Description	Flows
openid	Required by OpenID Connect Core 1.0 to request an ID token and identify the authenticated Everlywell member.	authorizationCode, password
public	Declared in scopes_supported by the authorization server. Everly Health publishes no definition for it; recorded verbatim without interpretation.	authorizationCode, password

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-04'
method: searched
source: https://secure.everlywell.com/.well-known/openid-configuration
docs: null
note: >-
  Scopes were read from scopes_supported in the anonymously published OpenID Connect
  Discovery / RFC 8414 document. Everly Health publishes no scopes or permissions
  reference page, so descriptions below are the spec-defined meaning of the scope
  name only — nothing was invented on the provider's behalf.
schemes:
- name: oauth2
  source: well-known/everly-health-openid-configuration.json
  issuer: https://secure.everlywell.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://secure.everlywell.com/oauth2/authorize
    tokenUrl: https://secure.everlywell.com/oauth2/token
  - flow: password
    tokenUrl: https://secure.everlywell.com/oauth2/token
scopes:
- scope: openid
  description: >-
    Required by OpenID Connect Core 1.0 to request an ID token and identify the
    authenticated Everlywell member.
  flows:
  - authorizationCode
  - password
  sources:
  - well-known/everly-health-openid-configuration.json
- scope: public
  description: >-
    Declared in scopes_supported by the authorization server. Everly Health publishes
    no definition for it; recorded verbatim without interpretation.
  flows:
  - authorizationCode
  - password
  sources:
  - well-known/everly-health-openid-configuration.json
coverage:
  scopes_declared: 2
  granular_resource_scopes: 0
  note: >-
    Two scopes total. There is no resource-level scope surface — consent granularity
    is effectively all-or-nothing for anything beyond OIDC identity.
x-evidence:
  fetched: '2026-08-04'
  url: https://secure.everlywell.com/.well-known/openid-configuration
  http_status: 200
  content_type: application/json