Recorded Future · OAuth Scopes

Recorded Future OAuth Scopes

OAuth 2.0 none

Recorded Future 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://id.recordedfuture.com/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.

CybersecurityThreat IntelligenceIntelligence CloudBrand IntelligenceIdentity IntelligenceVulnerability IntelligenceAI Analyst
Scopes: 0 Flows: authorizationCode Method: none

OAuth endpoints

Authorization URL
https://id.recordedfuture.com/authorize
Token URL
https://id.recordedfuture.com/token
Flows
authorizationCode

Scopes (0)

Recorded Future 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.

The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-10-20'
method: none
source: openapi/recorded-future-analyst-note-api-openapi.yml, openapi/recorded-future-autonomous-threat-operations-api-openapi.yml,
  openapi/recorded-future-case-api-openapi.yml, openapi/recorded-future-collective-insights-api-openapi.yml,
  openapi/recorded-future-detection-rule-api-openapi.yml, openapi/recorded-future-detection-rule-relation-api-openapi.yml,
  openapi/recorded-future-entity-match-api-openapi.yml, openapi/recorded-future-fusion-api-openapi.yml,
  openapi/recorded-future-identity-api-openapi.yml, openapi/recorded-future-links-api-openapi.yml,
  openapi/recorded-future-list-api-openapi.yml, openapi/recorded-future-malware-intelligence-api-openapi.yml,
  openapi/recorded-future-playbook-alerts-api-openapi.yml, openapi/recorded-future-risk-api-openapi.yml,
  openapi/recorded-future-threat-api-openapi.yml
schemes:
- name: idp
  source: openapi/recorded-future-analyst-note-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: idp
  source: openapi/recorded-future-autonomous-threat-operations-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: OAuth 2.0 Authorization Code Flow. This API issues and accepts JWTs that are
    compliant with RFC8725 (JSON Web Token Best Current Practices).
- name: idp
  source: openapi/recorded-future-case-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: idp
  source: openapi/recorded-future-collective-insights-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: idp
  source: openapi/recorded-future-detection-rule-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
- name: idp
  source: openapi/recorded-future-detection-rule-relation-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
- name: idp
  source: openapi/recorded-future-entity-match-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
- name: idp
  source: openapi/recorded-future-fusion-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: RecordedFutureOAuth2
  source: openapi/recorded-future-identity-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: JWT-based OAuth2 security scheme supporting RFC8725 for OAuth 2.0 Access Tokens.
- name: idp
  source: openapi/recorded-future-links-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: idp
  source: openapi/recorded-future-list-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
- name: idp
  source: openapi/recorded-future-malware-intelligence-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: idp
  source: openapi/recorded-future-playbook-alerts-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: idp
  source: openapi/recorded-future-risk-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
- name: idp
  source: openapi/recorded-future-threat-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.recordedfuture.com/authorize
    tokenUrl: https://id.recordedfuture.com/token
  description: Click on "Authorize" to be redirected to the login page.
scopes: []
note: The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement
  references one.

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/recorded-future-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.