Saxo Bank · OAuth Scopes
Saxo Bank OAuth Scopes
OAuth 2.0
derived
Saxo Bank 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://sim.logonvalidation.net/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.
Investment BankingTradingEquitiesForexOptionsFuturesMarket DataPortfolio ManagementOrdersFinancial
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://sim.logonvalidation.net/authorize
https://sim.logonvalidation.net/authorize
Token URL
https://sim.logonvalidation.net/token
https://sim.logonvalidation.net/token
Flows
authorizationCode
authorizationCode
Scopes (0)
Saxo Bank 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.
Saxo Bank OpenAPI does not use OAuth scopes ("scope - Not used" in the authorization code grant docs); access is governed by claims-based access control, with token claims granting Read/Subscribe/Write on resource access levels (https://developer.saxobank.com/openapi/learn/security).
Saxo Bank OpenAPI does not use OAuth scopes ("scope - Not used" in the authorization code grant docs); access is governed by claims-based access control, with token claims granting Read/Subscribe/Write on resource access levels (https://developer.saxobank.com/openapi/learn/security).
📄 Provider scope reference: https://developer.saxobank.com/openapi/learn/security