How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

dxFeed Historical Return Controller API

The historical-return-controller API from dxFeed — 6 operation(s) for historical-return-controller.

dxFeed Historical Return Controller API is one of 36 APIs that dxFeed publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include historical-return-controller. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 6 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://tools.dxfeed.com/fs.

9 operations 6 paths 8 schemas 1 DELETE5 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://demo.dxfeed.com/webservice/rest
Resource Areas
1

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 1 DELETE, 5 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

historical-return-controller 9
POST
/v0.1/historical-return
addManualCorrection_12 body → 403406500400503200
DELETE
/v0.1/historical-return
addManualRemove_12 body → 403406500400503200
GET
/v0.1/historical-return/recent/snapshot
getRecentSnapshot_13 5 params → 403406500400503200
POST
/v0.1/historical-return/recent/snapshot
postRecentSnapshot_13 1 param body → 403406500400503200
GET
/v0.1/historical-return/filter
getDeepFilter_13 12 params → 403406500400503200
POST
/v0.1/historical-return/filter
postDeepFilter_13 body → 403406500400503200
GET
/v0.1/historical-return/ymd/{ymd}
getDeepYmd_12 2 params → 403406500400503200
GET
/v0.1/historical-return/symbol/{symbol}
getDeepSymbol_13 2 params → 403406500400503200
GET
/v0.1/historical-return/recent/symbol/{symbol}
getRecentSymbol_13 3 params → 403406500400503200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PeriodicHistoryFilterParams (13 properties), HistoricalReturn (11 properties), FundamentalIdentityObject (9 properties), ApiError (4 properties). Each schema is shown below with its type and property counts.

Ext
object
ApiError
object
4 properties
PeriodicHistoryFilterParams
object
13 properties
FundamentalIdentityObject
object
9 properties 1 required
HistoricalReturn
object
11 properties
Period
object
RecentSnapshotFilterParam
object
4 properties
Map
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dxfeed-historical-return-controller-api-openapi.yml Raw ↑

Other APIs dxFeed publishes across the network.

dxFeed REST Web Service API
dxFeed dxLink WebSocket API
dxFeed Instrument Profile (IPF) Web Service
dxFeed FIX API
dxFeed Historical Data Services
dxFeed Alpha Beta Controller API
dxFeed Asset Classification Controller API
dxFeed Balance Statement Controller API
dxFeed Cash Flow Statement Controller API
dxFeed Company Profile Controller API
dxFeed Consensus Estimate Controller API
dxFeed Corporate Action Controller API
Where this information came from

This is an independent, third-party profile of dxFeed Historical Return Controller API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.