Hidden Road · OAuth Scopes

Hidden Road OAuth Scopes

OAuth 2.0 probed

Hidden Road 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.

CompanyFinancial-ServicesPrime BrokerageClearingDigital AssetsForeign ExchangeCapital MarketsTradingInstitutional FinanceCollateral ManagementRisk ManagementRegulated

Scopes: 0 Flows: Method: probed

Scopes (0)

Hidden Road 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.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-22'
method: probed
source: >-
  https://portal.ops.hiddenroad.com/assets/index-b9a72e77.js (HTTP 200, unauthenticated
  first-party bundle) and https://auth.hiddenroad.com/.well-known/openid-configuration (HTTP 200)
docs: null
docs_note: >-
  Hidden Road publishes NO scopes or permissions reference. The API scopes below were read
  verbatim out of the Operational Portal's own public JavaScript bundle, where they appear in
  the Auth0 token request alongside audience "https://api.hiddenroad.com/v0/". Treat the list as
  a floor, not a complete vocabulary: it is only the set the ops portal itself requests, so
  scopes for the metrics (Risk) and atm (Automated Treasury Management) services are almost
  certainly defined and simply not present in this bundle.
authorization_server: https://auth.hiddenroad.com/
audience: https://api.hiddenroad.com/v0/
flows:
- client_credentials
- authorization_code
api_scopes:
- scope: 'otc:read'
  service: otc
  access: read
  description: >-
    Read access to the OTC surface under https://api.hiddenroad.com/v0/otc/. Verbatim from the
    portal bundle; Hidden Road publishes no description of its own.
- scope: 'otc:write'
  service: otc
  access: write
  description: >-
    Write access to the OTC surface. This is the only confirmed write scope on the API and the
    reason the reversibility question in conventions/ matters for this provider.
- scope: 'accountactivity:*'
  service: accountactivity
  access: wildcard
  description: >-
    Wildcard grant over the Account Activity API (balances, trades, positions, fees). A `*`
    scope is coarse: an integrator cannot request read-only account activity with the vocabulary
    as published.
oidc_scopes:
  requested_by_portal: [openid, profile, email]
  supported:
  - openid
  - profile
  - offline_access
  - name
  - given_name
  - family_name
  - nickname
  - email
  - email_verified
  - picture
  - created_at
  - identities
  - phone
  - address
services_without_published_scopes:
- service: metrics
  path: https://api.hiddenroad.com/v0/metrics/
  product: Risk API
  status: 401 (route confirmed live, scope vocabulary unknown)
- service: atm
  path: https://api.hiddenroad.com/v0/atm/
  product: Automated Treasury Management API
  status: 401 (route confirmed live, scope vocabulary unknown)

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/hidden-road-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.