dxFeed · Authentication Profile

Dxfeed Authentication

Authentication

dxFeed secures its APIs with http-basic (login/password credentials) and dxLink AUTH token (protocol message) across 3 declared security schemes, as derived from its OpenAPI definitions.

FinancialMarket DataReal-TimeHistorical DataEquitiesOptionsFuturesCryptoReference DataFundamentals
Methods: http-basic (login/password credentials), dxLink AUTH token (protocol message) Schemes: 3 OAuth flows: API key in:

Security Schemes

credentials http
scheme: basic
dxlink-auth protocol-message
fundamentals-openapi none-declared

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-22'
method: searched
docs: https://kb.dxfeed.com/en/getting-started.html
source: kb.dxfeed.com docs + asyncapi/dxfeed-dxlink-asyncapi.yml + live probes
summary:
  types:
  - http-basic (login/password credentials)
  - dxLink AUTH token (protocol message)
  self_serve: false
  note: No OAuth, no self-serve API keys. Production credentials (endpoint URLs, login, password) plus
    per-service entitlements are issued during sales onboarding. Public demo endpoints (demo.dxfeed.com
    REST webservice, wss://demo.dxfeed.com/dxlink-ws) require no credentials and serve delayed data.
schemes:
- name: credentials
  type: http
  scheme: basic
  description: Login/password credentials with per-service entitlements for REST webservice, IPF web service
    (tools.dxfeed.com/ipf returns 401 without them), Fundamentals production, and historical/tick extraction.
  sources:
  - https://kb.dxfeed.com/en/data-model/reference-data/ipf-webservice.html
  - 'live probe: tools.dxfeed.com/ipf HTTP 401'
- name: dxlink-auth
  type: protocol-message
  description: 'dxLink WebSocket protocol authentication: after SETUP, the server sends AUTH_STATE UNAUTHORIZED
    and the client sends an AUTH message carrying a token; the server replies AUTH_STATE AUTHORIZED. Token
    issuance is part of dxFeed onboarding; the demo server does not require auth.'
  sources:
  - asyncapi/dxfeed-dxlink-asyncapi.yml
- name: fundamentals-openapi
  type: none-declared
  description: The Fundamentals OpenAPI (tools.dxfeed.com/fs/v3/api-docs) declares no securitySchemes;
    entitlements are enforced out-of-band (403 responses declared on every operation; live production
    endpoints are credential-gated).
  sources:
  - openapi/dxfeed-fundamentals-openapi.json

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact 
curl "https://apis.io/api/v1/security/dxfeed-authentication"
All security posture 
curl "https://apis.io/api/v1/security?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.