SS&C Technologies · OAuth Scopes
SS&C Technologies OAuth Scopes
OAuth 2.0
probed
SS&C Technologies 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.
Financial-ServicesInvestment ManagementFund AdministrationWealth ManagementExecution ManagementOrder ManagementMarket DataTradinggRPCEnterprise Software
Scopes: 0
Flows:
Method: probed
Scopes (0)
SS&C Technologies 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.
These are the scopes_supported values the SS&C APIM Keycloak realm advertises in its own OpenID Connect discovery document, read anonymously on 2026-09-13. They are NOT derived from an OpenAPI: the Eze EMS xAPI spec declares no oauth2 securityScheme, so there is no scope surface to derive there. Most entries below are Keycloak built-ins; only events_enrichment_api_member and voucher are realm-specific, and SS&C publishes no scope reference page describing what either grants — the portal's own documentation is behind SSO.
These are the scopes_supported values the SS&C APIM Keycloak realm advertises in its own OpenID Connect discovery document, read anonymously on 2026-09-13. They are NOT derived from an OpenAPI: the Eze EMS xAPI spec declares no oauth2 securityScheme, so there is no scope surface to derive there. Most entries below are Keycloak built-ins; only events_enrichment_api_member and voucher are realm-specific, and SS&C publishes no scope reference page describing what either grants — the portal's own documentation is behind SSO.
📄 Provider scope reference: https://developer.ssctech.com/
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.