Exchange-Specific Trading API Constraints and Symbol Formats
Summary
This guide collects exchange-specific implementation details for brokerage and cryptocurrency connections. For Futu, it explains market-specific stock symbol formats, account market identification, and the effect of disabling cached account and position data on query limits. It also notes that FutuOpenD behavior can depend on the login region. Interactive Brokers setup requires a running TWS or IB Gateway configured for socket access; the guide says its integration supports US equities only.
The remaining notes cover practical API and execution constraints across several venues. Examples include how to switch API base addresses, set supported symbols, and configure test environments, along with limitations such as missing open-order or trade-history endpoints and candlestick data that omits the current bar. Some spot market-buy interfaces interpret order quantity as units of the asset rather than quote currency. These are integration references, not a strategy guide, and the details are venue-specific and may change as APIs evolve.
Key ideas
- Futu account and position queries use cached data by default, while disabling the cache introduces a stated query limit.
- Futu stock symbols encode their market suffix, and account data identifies the associated trading market.
- The guide describes Interactive Brokers setup requirements and limits its supported market to US equities.
- Exchange integrations differ in available endpoints, bar data, order quantity conventions, and configuration options.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.