Darrow · OAuth Scopes
Darrow OAuth Scopes
OAuth 2.0
probed
Darrow 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.
CompanyLegalLegal IntelligenceLitigationArtificial IntelligenceComplianceRisk ManagementInsuranceData Analytics
Scopes: 0
Flows:
Method: probed
Scopes (0)
Darrow 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 advertised by Darrow's Auth0 identity tenant, read from `scopes_supported` in its OpenID Connect discovery document. They are the standard OIDC/Auth0 profile scopes — Darrow publishes no product API and therefore no API-specific permission scopes. Absence of custom scopes here is a finding, not a gap in the probe: no public resource-server metadata or scope reference exists.
These are the scopes advertised by Darrow's Auth0 identity tenant, read from `scopes_supported` in its OpenID Connect discovery document. They are the standard OIDC/Auth0 profile scopes — Darrow publishes no product API and therefore no API-specific permission scopes. Absence of custom scopes here is a finding, not a gap in the probe: no public resource-server metadata or scope reference exists.