Open Grimmble opened 2 years ago
Small update:
This seem specific to stop_limit
type crypto orders. E.g. for SOLUSD
:
Tried placing a market
order and a new
+ fill
event was immidately picked up by the client.StreamTradeUpdates()
handler.
Then I tried placing a stop_limit
order and no new
event is picked up by the client.StreamTradeUpdates()
handler (even though it show up in the Alpaca UI as "new")
Hi,
Ver:
github.com/alpacahq/alpaca-trade-api-go/v2 v2.5.0
Seems that trade updates using the
client.StreamTradeUpdates()
functionality differ quite a bit from stocks to crypto. For stocks I would be notified of anynew
,rejected
,fill
etc. type of events, doesn't seem to be the case for crypto where I've only been able to getcanceled
events.Is there a different implementation for crypto streams? Or are the events different for crypto? (the docs doesn't give a clear indication about this)
NOTE: The code below works fine for stocks