Cronometer · OAuth Scopes
Cronometer OAuth Scopes
OAuth 2.0
none
Cronometer 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.
CompanyNutritionHealthFitnessCalorie CounterDiet TrackingMobile AppWellness
Scopes: 0
Flows:
Method: none
Scopes (0)
Cronometer 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.
No public API documentation found; provider does not publish a public developer API
No public API documentation found; provider does not publish a public developer API
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.