Halaxy · OAuth Scopes
Halaxy OAuth Scopes
OAuth 2.0
none
Halaxy 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 /main/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.
CompanyHealthcarePractice ManagementFHIRTelehealthAppointmentsBillingPatients
Scopes: 0
Flows: clientCredentials
Method: none
OAuth endpoints
Token URL
/main/oauth/token
/main/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Halaxy 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.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one. The docs publish no OAuth scope reference either; access is set per API key in the Halaxy API Key Manager ("Check the API Key Manager in Halaxy - does your API key have appropriate access for the request objective? (You can check this in Settings > Integrations > External)").
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one. The docs publish no OAuth scope reference either; access is set per API key in the Halaxy API Key Manager ("Check the API Key Manager in Halaxy - does your API key have appropriate access for the request objective? (You can check this in Settings > Integrations > External)").
📄 Provider scope reference: https://developers.halaxy.com/docs/troubleshooting-guide.md
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.