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.

Source

OAuth Scopes

Raw ↑
generated: '2026-09-13'
method: probed
source: https://ssoprod.ssnc.cloud/auth/realms/APIM/.well-known/openid-configuration
docs: https://developer.ssctech.com/
applies_to: SS&C APIM Developer Portal (developer.ssctech.com / apim.ssnc.cloud)
note: >-
  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.
scope_count: 14
provider_specific_scope_count: 2
pkce_supported:
- plain
- S256
scopes:
- name: openid
  description: OpenID Connect authentication request marker (standard).
  standard: true
- name: profile
  description: Basic profile claims (standard OIDC claim set).
  standard: true
- name: email
  description: Email address claims (standard OIDC claim set).
  standard: true
- name: address
  description: Address claims (standard OIDC claim set).
  standard: true
- name: phone
  description: Phone number claims (standard OIDC claim set).
  standard: true
- name: roles
  description: Keycloak realm and client role claims.
  standard: true
- name: web-origins
  description: Keycloak CORS allowed-origins claim.
  standard: true
- name: acr
  description: Authentication context class reference (standard).
  standard: true
- name: basic
  description: Keycloak basic claim set (sub, auth_time).
  standard: true
- name: microprofile-jwt
  description: Eclipse MicroProfile JWT claim mapping (upn, groups).
  standard: true
- name: offline_access
  description: Requests a refresh token usable while the user is offline (standard).
  standard: true
- name: service_account
  description: Keycloak service-account client scope, used for client_credentials grants.
  standard: true
- name: events_enrichment_api_member
  description: >-
    Realm-specific scope. Its name binds it to an SS&C events-enrichment API product surfaced
    through the APIM gateway. SS&C publishes no description of what it grants; recorded verbatim
    from scopes_supported.
  standard: false
- name: voucher
  description: >-
    Realm-specific scope with no published description. Recorded verbatim from scopes_supported.
  standard: false
grant_types_supported:
- authorization_code
- client_credentials
- implicit
- password
- refresh_token
- urn:ietf:params:oauth:grant-type:device_code
- urn:ietf:params:oauth:grant-type:jwt-bearer
- urn:ietf:params:oauth:grant-type:token-exchange
- urn:ietf:params:oauth:grant-type:uma-ticket
- urn:openid:params:grant-type:ciba

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/ss-c-technologies-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.

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