AirPR · OAuth Scopes

AirPR OAuth Scopes

OAuth 2.0 probed

AirPR publishes 4 OAuth 2.0 scopes via the authorizationCode and implicit flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the AirPR API on a user’s behalf.

Tokens are issued from https://crawler-api-auth.onclusive.com/oauth2/token.

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.

CompanyPublic RelationsMedia IntelligenceMedia MonitoringAnalyticsCommunicationsMarketingPR MeasurementOnclusive

Scopes: 4 Flows: authorizationCode, implicit Method: probed

OAuth endpoints

Authorization URL
https://crawler-api-auth.onclusive.com/oauth2/authorize

Token URL
https://crawler-api-auth.onclusive.com/oauth2/token

Flows
authorizationCodeimplicit

Scopes (4)

Scope	Description	Flows
openid	Standard OpenID Connect scope; requests an ID token identifying the authenticated developer-portal user.	authorizationCode, implicit
email	Releases the user's email address and email_verified claim.	authorizationCode, implicit
phone	Releases the user's phone_number and phone_number_verified claims.	authorizationCode, implicit
profile	Releases the user's basic profile claims.	authorizationCode, implicit

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_F0XmSWr9T/.well-known/openid-configuration
note: >-
  These are the scopes the Onclusive developer-portal authorization server
  actually advertises in its OIDC discovery document. They are the four standard
  OpenID Connect scopes and nothing more — Onclusive has defined no custom
  resource-server scopes on this user pool, or has not exposed them in
  discovery. NOT derived from an OpenAPI: Onclusive publishes none. No
  API-permission or scope reference page exists on any public Onclusive URL, so
  there is no richer `docs:` to point at.
schemes:
- name: OnclusiveDeveloperPortalOIDC
  type: openIdConnect
  source: well-known/airpr-openid-configuration.json
  issuer: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_F0XmSWr9T
  flows:
  - flow: authorizationCode
    authorizationUrl: https://crawler-api-auth.onclusive.com/oauth2/authorize
    tokenUrl: https://crawler-api-auth.onclusive.com/oauth2/token
  - flow: implicit
    authorizationUrl: https://crawler-api-auth.onclusive.com/oauth2/authorize
scopes:
- scope: openid
  description: >-
    Standard OpenID Connect scope; requests an ID token identifying the
    authenticated developer-portal user.
  standard: true
  flows: [authorizationCode, implicit]
  sources: [well-known/airpr-openid-configuration.json]
- scope: email
  description: Releases the user's email address and email_verified claim.
  standard: true
  flows: [authorizationCode, implicit]
  sources: [well-known/airpr-openid-configuration.json]
- scope: phone
  description: Releases the user's phone_number and phone_number_verified claims.
  standard: true
  flows: [authorizationCode, implicit]
  sources: [well-known/airpr-openid-configuration.json]
- scope: profile
  description: Releases the user's basic profile claims.
  standard: true
  flows: [authorizationCode, implicit]
  sources: [well-known/airpr-openid-configuration.json]
scope_count: 4
custom_scope_count: 0
x-evidence:
- url: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_F0XmSWr9T/.well-known/openid-configuration
  status: 200