CentralReach · Authentication Profile

Centralreach Authentication

Authentication

The CentralReach Enhanced API requires two credentials on every request: an organization-scoped API key sent in the x-api-key header, and an OAuth 2.0 Bearer access token obtained via the client-credentials grant against the CentralReach identity provider. Credentials (client_id, client_secret, and the CR API key) are issued by the CentralReach Implementation Team; the API is not self-serve. Access tokens are RS256 JWTs with a one-hour lifetime carrying iss, exp, sub, and orgid claims.

CentralReach secures its APIs with oauth2 and apiKey across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyHealthcareABA TherapyAutismIDDEMRPractice ManagementBehavioral HealthSpecial EducationBillingOAuth
Methods: oauth2, apiKey Schemes: 2 OAuth flows: clientCredentials API key in: header

Security Schemes

clientCredentials oauth2
apiKey apiKey
· in: header ()

Source

Authentication Profile

centralreach-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://login.centralreach.com/.well-known/openid-configuration
docs: https://centralreach.com/resources/api/
summary:
  types: [oauth2, apiKey]
  api_key_in: [header]
  api_key_name: x-api-key
  oauth2_flows: [clientCredentials]
  identity_provider: https://login.centralreach.com
  token_signing_alg: RS256
  access_token_ttl_seconds: 3600
description: >-
  The CentralReach Enhanced API requires two credentials on every request: an
  organization-scoped API key sent in the x-api-key header, and an OAuth 2.0
  Bearer access token obtained via the client-credentials grant against the
  CentralReach identity provider. Credentials (client_id, client_secret, and the
  CR API key) are issued by the CentralReach Implementation Team; the API is not
  self-serve. Access tokens are RS256 JWTs with a one-hour lifetime carrying iss,
  exp, sub, and orgid claims.
schemes:
- name: clientCredentials
  type: oauth2
  flow: clientCredentials
  tokenUrl: https://login.centralreach.com/connect/token
  token_endpoint_auth_methods: [client_secret_basic, client_secret_post]
  scopes: [openid, cr, cr-api, offline_access]
  sources: [https://login.centralreach.com/.well-known/openid-configuration]
- name: apiKey
  type: apiKey
  in: header
  parameter_name: x-api-key
  description: Organization-specific API key issued by the CentralReach Implementation Team.
  sources: [https://centralreach.com/resources/api/]
oidc:
  issuer: https://login.centralreach.com
  authorization_endpoint: https://login.centralreach.com/connect/authorize
  token_endpoint: https://login.centralreach.com/connect/token
  userinfo_endpoint: https://login.centralreach.com/connect/userinfo
  jwks_uri: https://login.centralreach.com/.well-known/openid-configuration/jwks
  introspection_endpoint: https://login.centralreach.com/connect/introspect
  revocation_endpoint: https://login.centralreach.com/connect/revocation
  grant_types_supported: [authorization_code, client_credentials, refresh_token, implicit, password, 'urn:ietf:params:oauth:grant-type:device_code', 'urn:openid:params:grant-type:ciba']
  code_challenge_methods_supported: [plain, S256]