Cleo · OAuth Scopes
Cleo OAuth Scopes
OAuth 2.0
none
Cleo 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.
CompanyFamilyParentingBaby TrackingMeal PlanningMCPAI AssistantProductivity
Scopes: 0
Flows:
Method: none
Scopes (0)
Cleo 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.
The docs describe consent per data area ('When you connect, you choose what it gets, area by area: see, see and change, or off.') but do not publish OAuth scope strings, so none are recorded.
The docs describe consent per data area ('When you connect, you choose what it gets, area by area: see, see and change, or off.') but do not publish OAuth scope strings, so none are recorded.
📄 Provider scope reference: https://www.cleofamily.app/assistant/docs
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.