p*0
2 楼
他家api都提供什么?除了股票 option future quote有么?同时可以监视多少只股票?
谢谢
谢谢
n*x
4 楼
都有,不过只能监控100只股票. 监控时只能得到level 1的数据,没有level 2.也就是
说监控到的数据是每100 millisecond的一个snapshot...对于想做系统的IB的API还是
很有局限性.
说监控到的数据是每100 millisecond的一个snapshot...对于想做系统的IB的API还是
很有局限性.
w*n
5 楼
店里每年有几次活动,买满多少送手链
看你朋友要的是什么款式了。Ruelala的charm基本都是不好卖的款式。
她家charm款式太多,得看想要什么主题,是不是指定某几个。你就让她挑好给你发链
接你直接买吧,肯花这个钱买银饰的,基本也不差钱。
看你朋友要的是什么款式了。Ruelala的charm基本都是不好卖的款式。
她家charm款式太多,得看想要什么主题,是不是指定某几个。你就让她挑好给你发链
接你直接买吧,肯花这个钱买银饰的,基本也不差钱。
p*0
6 楼
可以得到历史数据么?
比如我1分钟扫一次,可以把这一分钟的交易都扫了么?
比如我1分钟扫一次,可以把这一分钟的交易都扫了么?
c*y
10 楼
Right, details
Historical data requests are subject to the following limitations:
l Historical data requests can go back one full calendar year.
l Each request is restricted to duration and bar size values that return no
more than 2000 bars (2000 bars per
request).
All of the API technologies support historical data requests. However,
requesting the same historical data in a short
period of time can cause extra load on the backend and subsequently cause
pacing violations. The error code and message
that indicates a pacing violation is:
162 - Historical Market Data Service error message: Historical data request
pacing violation
The following conditions can cause a pacing violation:
l Making identical historical data requests within 15 seconds;
l Making six or more historical data requests for the same Contract,
Exchange and Tick Type within two seconds.
Also, observe the following limitation when requesting historical data:
l Do not make more than 60 historical data requests in any ten-minute period.
【在 n**x 的大作中提到】
: 有历史数据,but 60 history data requests every 10 minutes, otherwise you
: will get pacing violation.
Historical data requests are subject to the following limitations:
l Historical data requests can go back one full calendar year.
l Each request is restricted to duration and bar size values that return no
more than 2000 bars (2000 bars per
request).
All of the API technologies support historical data requests. However,
requesting the same historical data in a short
period of time can cause extra load on the backend and subsequently cause
pacing violations. The error code and message
that indicates a pacing violation is:
162 - Historical Market Data Service error message: Historical data request
pacing violation
The following conditions can cause a pacing violation:
l Making identical historical data requests within 15 seconds;
l Making six or more historical data requests for the same Contract,
Exchange and Tick Type within two seconds.
Also, observe the following limitation when requesting historical data:
l Do not make more than 60 historical data requests in any ten-minute period.
【在 n**x 的大作中提到】
: 有历史数据,but 60 history data requests every 10 minutes, otherwise you
: will get pacing violation.
p*0
11 楼
thx
相关阅读