Revinate · OAuth Scopes
Revinate OAuth Scopes
OAuth 2.0
probed
Revinate 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.
HospitalityHotelsReviewsReputation ManagementGuest Data PlatformCRMSentiment AnalysisTravelMarketingCustomer Feedback
Scopes: 0
Flows:
Method: probed
Scopes (0)
Revinate 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 scopes are read verbatim from the scopes_supported array of Revinate's live OpenID Connect discovery document at auth.revinate.com, an Auth0-hosted issuer. IMPORTANT BOUNDARY: this issuer authenticates users into the Revinate web application; the public Porter REST API does not use OAuth at all and has no scope surface — it authenticates with four HMAC-SHA256 headers and access is provisioned per API key by a Revinate account manager. The scope list below is therefore the identity surface, not an API authorization surface. Every scope present is a standard OIDC scope or a standard OIDC claim-scope; Revinate declares no custom/product scopes.
These scopes are read verbatim from the scopes_supported array of Revinate's live OpenID Connect discovery document at auth.revinate.com, an Auth0-hosted issuer. IMPORTANT BOUNDARY: this issuer authenticates users into the Revinate web application; the public Porter REST API does not use OAuth at all and has no scope surface — it authenticates with four HMAC-SHA256 headers and access is provisioned per API key by a Revinate account manager. The scope list below is therefore the identity surface, not an API authorization surface. Every scope present is a standard OIDC scope or a standard OIDC claim-scope; Revinate declares no custom/product scopes.
📄 Provider scope reference: https://porter.revinate.com/documentation
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.