Paramark · OAuth Scopes
Paramark OAuth Scopes
OAuth 2.0
probed
Paramark 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.
CompanyApplicationsMarketingAnalyticsMeasurementMarketing Mix ModelingIncrementalityAdvertisingAI
Scopes: 0
Flows:
Method: probed
Scopes (0)
Paramark 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.
Read verbatim from the scopes_supported array of Paramark's own OpenID Connect discovery document and confirmed identical in its OAuth 2.0 Authorization Server Metadata document. These are the four standard OIDC scopes; Paramark advertises no product- or resource-scoped permissions at the authorization server, and publishes no scopes/permissions reference page. Nothing here is inferred — no API-level scope vocabulary was found, and none is invented.
Read verbatim from the scopes_supported array of Paramark's own OpenID Connect discovery document and confirmed identical in its OAuth 2.0 Authorization Server Metadata document. These are the four standard OIDC scopes; Paramark advertises no product- or resource-scoped permissions at the authorization server, and publishes no scopes/permissions reference page. Nothing here is inferred — no API-level scope vocabulary was found, and none is invented.