Simon Data · OAuth Scopes

Simon Data OAuth Scopes

OAuth 2.0 searched

Simon Data 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.

Tokens are issued from https://app.simondata.com/mcp/oauth/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.

Customer Data PlatformCDPMarketing AutomationAudience SegmentationEvent TrackingData IngestionPersonalizationMarketing TechnologyIdentity ResolutionCustomer ProfilesJourney OrchestrationSnowflake
Scopes: 0 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://app.simondata.com/mcp/oauth/authorize
Token URL
https://app.simondata.com/mcp/oauth/token
Flows
authorizationCode

Scopes (0)

Simon Data 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.

Simon Data publishes no OAuth scope vocabulary. The Audience API uses opaque bearer tokens issued by a Client Solutions Manager, and the Event Ingestion API uses a shared partnerSecret in the payload — neither has a scope surface. The one OAuth authorization server Simon does publish, the MCP metadata document at https://app.simondata.com/.well-known/oauth-authorization-server, omits scopes_supported entirely. Recorded as a real zero, not a gap.

📄 Provider scope reference: https://docs.simondata.com/reference/getting-started

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-13'
method: searched
source: https://docs.simondata.com/reference/getting-started
docs: https://docs.simondata.com/reference/getting-started
note: >-
  Simon Data publishes no OAuth scope vocabulary. The Audience API uses opaque bearer tokens issued by a Client
  Solutions Manager, and the Event Ingestion API uses a shared partnerSecret in the payload — neither has a scope
  surface. The one OAuth authorization server Simon does publish, the MCP metadata document at
  https://app.simondata.com/.well-known/oauth-authorization-server, omits scopes_supported entirely. Recorded as a real
  zero, not a gap.
schemes:
- name: mcp-oauth
  source: well-known/simon-data-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://app.simondata.com/mcp/oauth/authorize
    tokenUrl: https://app.simondata.com/mcp/oauth/token
  description: MCP authorization server; scopes_supported is absent from the published metadata.
scopes: []
scope_count: 0

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/simon-data-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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