Clever Care Health Plan · Authentication Profile

Clevercarehealthplan Authentication

Authentication

Clever Care Health Plan secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

CompanyHealthcareHealth InsuranceMedicare AdvantageFHIRInteroperabilityPatient AccessProvider DirectoryDrug Formulary
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

smartOnFhir oauth2
· flows: authorizationCode, clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/clevercarehealthplan-fhir-openapi.yml
docs: https://clevercarehealthplan.com/fhir-api-developer-resources/
notes: >-
  SMART-on-FHIR OAuth 2.0 with OpenID Connect, confirmed from the server
  /.well-known/smart-configuration and FHIR CapabilityStatement security.service
  (SMART-on-FHIR). PKCE S256 supported; token_endpoint_auth_methods
  client_secret_basic and client_secret_post; grant types authorization_code
  and client_credentials. Provider Directory and Drug Formulary resources are
  public (rate limited); Patient Access resources require OAuth 2.0.
summary:
  types:
  - oauth2
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: smartOnFhir
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://fhir-portal.clevercarehealthplan.com/oauth2/authorize
    tokenUrl: https://fhir-portal.clevercarehealthplan.com/oauth2/token
    scopes: 4
  - flow: clientCredentials
    tokenUrl: https://fhir-portal.clevercarehealthplan.com/oauth2/token
    scopes: 2
  description: SMART-on-FHIR OAuth 2.0 (PKCE S256), OpenID Connect enabled.
  sources:
  - openapi/clevercarehealthplan-fhir-openapi.yml