DIPS · OAuth Scopes
DIPS OAuth Scopes
OAuth 2.0
probed
DIPS 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.
CompanyHealthcareElectronic Health RecordsHealth ITFHIRopenEHRInteroperabilityIdentityOpenID ConnectNorwayHospitalsSMART on FHIR
Scopes: 0
Flows:
Method: probed
Scopes (0)
DIPS 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.
Read live, unauthenticated, from the DIPS Federation Service OpenID Connect discovery document on 2026-09-02 (saved verbatim at well-known/dips-openid-configuration.json). Descriptions are supplied by API Evangelist only where the scope name is self-describing or is documented on the Open DIPS getting-started page; scopes DIPS does not document carry description: null rather than a guess. DIPS publishes no scopes/permissions reference page.
Read live, unauthenticated, from the DIPS Federation Service OpenID Connect discovery document on 2026-09-02 (saved verbatim at well-known/dips-openid-configuration.json). Descriptions are supplied by API Evangelist only where the scope name is self-describing or is documented on the Open DIPS getting-started page; scopes DIPS does not document carry description: null rather than a guess. DIPS publishes no scopes/permissions reference page.
📄 Provider scope reference: https://dips.developer.azure-api.net/getting-started
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.