Sparrow · OAuth Scopes
Sparrow OAuth Scopes
OAuth 2.0
probed
Sparrow 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.
CompanyLeave ManagementHuman ResourcesHR TechPayrollComplianceEmployee BenefitsAbsence ManagementSoftware-as-a-Service
Scopes: 0
Flows:
Method: probed
Scopes (0)
Sparrow 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.
These are the scopes the anonymously-published OIDC discovery document on Sparrow's own sign-in domain advertises as supported. They are the standard OpenID Connect / Auth0 identity scopes for application sign-in — Sparrow publishes NO product or resource scopes, because it publishes no third-party API. Nothing here was authored by API Evangelist; the list is verbatim from scopes_supported.
These are the scopes the anonymously-published OIDC discovery document on Sparrow's own sign-in domain advertises as supported. They are the standard OpenID Connect / Auth0 identity scopes for application sign-in — Sparrow publishes NO product or resource scopes, because it publishes no third-party API. Nothing here was authored by API Evangelist; the list is verbatim from scopes_supported.
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.