TailorMed · OAuth Scopes
TailorMed OAuth Scopes
OAuth 2.0
probed
TailorMed 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.
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.
CompanyHealthcareHealth ITMedication AccessMedication AffordabilityFinancial NavigationPatient AssistancePharmacyOncologyRevenue CycleHL7FHIRLife Sciences
Scopes: 0
Flows:
Method: probed
Scopes (0)
TailorMed 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.
These are platform sign-in scopes. The Application Data API, Claims Data API and HL7/FHIR data-exchange surfaces are documented only behind the login on hub.tailormed.co, so any API-specific scope or permission model they use is not publicly readable.
These are platform sign-in scopes. The Application Data API, Claims Data API and HL7/FHIR data-exchange surfaces are documented only behind the login on hub.tailormed.co, so any API-specific scope or permission model they use is not publicly readable.
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.