Simon Data · OAuth Scopes
Simon Data OAuth Scopes
OAuth 2.0
derived
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://api.simondata.com/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 Technology
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.simondata.com/oauth/token
https://api.simondata.com/oauth/token
Flows
clientCredentials
clientCredentials
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 does not publish OAuth scopes; its Audience/Contact API uses bearer tokens issued by a Client Solutions Manager and the Signal event API uses a shared partner secret, with OAuth 2.0 only referenced for outbound integrations to third-party systems (https://docs.simondata.com/reference/getting-started).
Simon Data does not publish OAuth scopes; its Audience/Contact API uses bearer tokens issued by a Client Solutions Manager and the Signal event API uses a shared partner secret, with OAuth 2.0 only referenced for outbound integrations to third-party systems (https://docs.simondata.com/reference/getting-started).
📄 Provider scope reference: https://docs.simondata.com/reference/getting-started