hi.health · OAuth Scopes
hi.health OAuth Scopes
OAuth 2.0
searched
hi.health publishes 3 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the hi.health API on a user’s behalf.
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.
CompanyInsurancePaymentsCardsFintechHealthCards-as-a-ServiceEmbedded FinanceReimbursementClaims
Scopes: 3
Flows:
Method: searched
Scopes (3)
| Scope | Description | Flows |
|---|---|---|
| sync | Sync scope: read/expense-management integration for pulling card, transaction and receipt data into a partner's own application (expense management use case). | |
| embedded-wallet | Embedded Wallet scope: embed Pliant cards and wallet functionality inside a partner application. | |
| fully-embedded | Fully Embedded scope: the deepest integration tier, embedding the full card-issuing and management lifecycle in the partner product. |
📄 Provider scope reference: https://partner.getpliant.com/docs/introduction-to-scopes.md