CentralReach · OAuth Scopes
CentralReach OAuth Scopes
OAuth 2.0
searched
CentralReach publishes 4 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the CentralReach API on a user’s behalf.
Tokens are issued from https://login.centralreach.com/connect/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.
CompanyHealthcareABA TherapyAutismIDDEMRPractice ManagementBehavioral HealthSpecial EducationBillingAuthentication
Scopes: 4
Flows: clientCredentials
Method: searched
OAuth endpoints
Token URL
https://login.centralreach.com/connect/token
https://login.centralreach.com/connect/token
Flows
clientCredentials
clientCredentials
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| openid | OpenID Connect authentication scope; requests an ID token identifying the subject. | clientCredentials |
| cr | CentralReach platform access scope. | clientCredentials |
| cr-api | Access to the CentralReach Enhanced API (partners-api enterprise endpoints). | clientCredentials |
| offline_access | Requests a refresh token for long-lived, offline access. | clientCredentials |
📄 Provider scope reference: https://community.centralreach.com/s/article/knowledge-api-permissions
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.