Bookmap forum

Ah, got you... Unfortunately this information is not currently available. It's not something we can put into InstrumentInfo  since it changes on the fly, so to expose it we'd need some separate interface. Not sure how important having this in API is...

It's purely a visual setting affecting how frequent the prices will be on the price scale. It can be changed at any point and does not affect the instrument, thus it's not exposed through API.

Could you provide a use case where you need it?

Yes

Hi. You are not taking pips (min tick) into account. The numbers you are seeing are effectively level numbers (which are integers), not raw prices. You need to multiply by pips to get an actual price.

Hi. Binance decided to block US customers from accessing their API. They were rolling out the changes over some interval of time, but looks like right now it's affecting most users. This is outside of our control since their services will simply block your request if you are in certain countries.

Hi. It's already available, though it is in alpha (7.4): https://bookmap.com/current/alpha/m1

If doing it in a headless way (i.e. no monitor connected) is not mandatory, you could simply use L1 API. Just connect to necessary exchanges via bookmap and do everything you need via L1

We don't currently support neither GTD nor GTT configuration from inside bookmap. As I mentioned, those only exist to handle orders sent by other platforms. It is a 100% valid feature request to allow that, but it's not something we have right now

Currently GTT duration is not fully supported, it's only there so we can correctly display GTT orders coming from external sources

If you are talking about the entry point caching - that is done based on the jar file hash, so as soon as you rebuild it (so that hash is different) - it should no longer be cached. That being said, if the above reply from Andrey and my reply didn't help - please record a video if possible to show t...