Flexpa · OAuth Scopes
Flexpa OAuth Scopes
OAuth 2.0
searched
Flexpa publishes 2 OAuth 2.0 scopes via the authorizationCode, clientCredentials, and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Flexpa API on a user’s behalf.
Tokens are issued from https://api.flexpa.com/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.
HealthcareFHIRPatient AccessClaims DataHealth Insurance
Scopes: 2
Flows: authorizationCode, clientCredentials, refreshToken
Method: searched
OAuth endpoints
Authorization URL
https://api.flexpa.com/oauth/authorize
https://api.flexpa.com/oauth/authorize
Token URL
https://api.flexpa.com/oauth/token
https://api.flexpa.com/oauth/token
Flows
authorizationCodeclientCredentialsrefreshToken
authorizationCodeclientCredentialsrefreshToken
Scopes (2)
| Scope | Description | Flows |
|---|---|---|
| launch/patient | SMART on FHIR standalone patient launch context. Required on every authorization URL; grants read access to the authorizing patient's compartment (Patient, Coverage, ExplanationOfBenefit and the clinical resources Flexpa derives). | |
| offline_access | Issues a refresh token so the application can continue retrieving the patient's data after the initial access token expires. Corresponds to the permission-offline SMART capability. |
📄 Provider scope reference: https://www.flexpa.com/docs/consent
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.