dxFeed APIs Overview
What is API?
An application programming interface (API) is a set of rules and standardized requests which allows communication between programs and services.
Current list of supported API
Java
C/C++/C#
REST
JavaScript/SSE/Websocket
FIX
Python
In development
R
Software Compatibility Matrix
Common
Product | Minimum Requirement |
|---|---|
TLS | 1.2 |
JRE (oracle) | 8.0 |
.NET studio | 4.6 |
Jetty | 9.2+ |
For C API
Language standard C is C11
For C++ language standard is C++11
API usage
Request types
dxFeed supports GET and POST requests:
Get | Post | |
|---|---|---|
BACK button/Reload | Harmless | Data will be re-submitted (the browser should alert the user that the data is about to be re-submitted) |
Bookmarked | Can be bookmarked | Cannot be bookmarked |
Cached | Can be cached | Not cached |
Encoding type | application/x-www-form-urlencoded | application/x-www-form-urlencoded or multipart/form-data. Use multipart encoding for binary data |
History | Parameters remain in browser history | Parameters are not saved in browser history |
Restrictions on data length | Yes, when sending data, the GET method adds the data to the URL; and the length of a URL is limited (maximum URL length is 2048 characters) | No restrictions |
Restrictions on data type | Only ASCII characters allowed | No restrictions. Binary data is also allowed |
Security | GET is less secure compared to POST because data sent is part of the URL. Never use GET when sending passwords or other sensitive information | POST is a little safer than GET because the parameters are not stored in browser history or in web server logs |
Visibility | Data is visible to everyone in the URL | Data is not displayed in the URL |
API integration
To successfully integrate dxFeed API:
Check out dxFeed documentation.
Take a look at dxFeed samples.
Can I use dxFeed on more than one computer at the same time?
You can use dxFeed on more than one computer at the same time. For this, all IP addresses should be whitelisted.
API integration
Product | Solution |
|---|---|
QD feed | Websocket |
News | News API |
Auther | Auther API |
SAS | Websocket |
IPF | Websocket |
Tickdata | Websocket |
Rest | Websocket (event.json) |
Orcs | ORCS API |
For any technical issues or questions, please check out the dxFeed API documentation. If your question is not answered, please go to the Help Desk, submit a ticket and provide the following information:
The exact timeframe (and timezone) of the issue (when it stopped working; when it started again).
Symbols you are requesting.
Logs collected (if any).
Code you are using to receive this data (or endpoint, or other connection/infrastructure details).
Any other details.
API code
Some dxFeed APIs have demo code on Github:
API authorization
dxFeed offers two types of authorization:
Token-based authorization
Web-based authorization
API Time
UTC and ISO 8601 formats are used as a standard
NTP is used for synchronizing