Zefr · OAuth Scopes
Zefr OAuth Scopes
OAuth 2.0
probed
Zefr 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.
CompanyAdtechBrand SafetyBrand SuitabilityContent IntelligenceContent ModerationVideoSocial MediaAdvertisingMedia MeasurementMachine Learning
Scopes: 0
Flows:
Method: probed
Scopes (0)
Zefr 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 Zefr's own identity provider (Auth0 custom domain login.zefr.com) advertises in its OpenID Connect discovery document, read verbatim. They are the standard OIDC identity-layer scopes — Zefr publishes NO product/API scope reference, and no audience-scoped permissions for any Zefr API. Recorded because they are genuinely published and machine-readable, not because they describe a product authorization model.
These are the scopes Zefr's own identity provider (Auth0 custom domain login.zefr.com) advertises in its OpenID Connect discovery document, read verbatim. They are the standard OIDC identity-layer scopes — Zefr publishes NO product/API scope reference, and no audience-scoped permissions for any Zefr API. Recorded because they are genuinely published and machine-readable, not because they describe a product authorization model.