RainFocus · OAuth Scopes

RainFocus OAuth Scopes

OAuth 2.0 probed

RainFocus 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.

CompanyEventEvent ManagementEvent MarketingRegistrationConferencesWebinarsMarketing TechnologyAttendee DataMCPAgentsEnterprise SoftwareSoftware-as-a-Service

Scopes: 0 Flows: Method: probed

Scopes (0)

RainFocus 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.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: https://api.rainfocus.com/.well-known/openid-configuration
docs: null
docs_note: >-
  RainFocus publishes no scopes or permissions reference page. Searching the public site and the
  API and MCP Tools terms turned up no scope names.
description: >-
  The only OAuth scope RainFocus advertises anywhere machine-readable is "openid", read from its
  own OIDC discovery document. RainFocus describes "short-lived, scoped access tokens" and
  "per-event scoping" for MCP Profiles, so a scope or permission vocabulary demonstrably exists
  inside the product - it is simply not published. No scope names are invented here.
authorization_server: https://events.rainfocus.com/oidc
scopes:
- name: openid
  description: >-
    Standard OpenID Connect scope requesting an ID token. Advertised in scopes_supported.
  source: '.well-known/openid-configuration scopes_supported'
scope_count: 1
undocumented_scoping_mechanisms:
- mechanism: API Profile
  description: >-
    Each RainFocus API Profile declares which endpoints are enabled (for example Attendee Store),
    which is the effective authorization boundary for the REST API. Profile names and the endpoint
    catalog are customer-specific and not published.
  source: https://experienceleague.adobe.com/en/docs/experience-platform/destinations/catalog/marketing-automation/rainfocus
- mechanism: MCP Profile per-event scoping
  description: >-
    Planners activate and control MCP tool access event by event, layered on per-user
    authentication and role-based access control.
  source: https://www.rainfocus.com/company/news-press/rainfocus-launches-ai-agent-connectivity-for-event-data-with-mcp-profiles/

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/rainfocus-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.