lovedone-app · OAuth Scopes
lovedone-app OAuth Scopes
OAuth 2.0
derived
lovedone-app publishes 4 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the lovedone-app API on a user’s behalf.
Tokens are issued from https://inbox.lovedone.app/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.
Family CareInboxHealthcareCommunicationPrivacy
Scopes: 4
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://inbox.lovedone.app/oauth/authorize
https://inbox.lovedone.app/oauth/authorize
Token URL
https://inbox.lovedone.app/oauth/token
https://inbox.lovedone.app/oauth/token
Flows
authorizationCode
authorizationCode
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| audit:read | Read the caller's agent activity log (internal — not advertised on the authorization server by default). | authorizationCode |
| care_circle:read | List loved ones and read recent care events. Required by list_loved_ones and list_care_events. | authorizationCode |
| care_circle:write | Invite family, add providers, send replies, and add notes or visits on your behalf. Required by invite_family_member, create_provider_code, reply_to_inbox_message, add_visit_note, and schedule_visit. | authorizationCode |
| profile:read | See the caller's name, email, and LovedOne workspace membership. Required by get_user_profile. | authorizationCode |
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.