Skip to content
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.

Support/encourage using IB activity statements only, not activity + trades #2

Open
jspahrsummers opened this issue May 6, 2019 · 1 comment
Labels
question Further information is requested

Comments

@jspahrsummers
Copy link
Member

bankroll-py/bankroll#35 introduces a query for activity statements, on top of the trade confirmation query recommended in the README. Activity statements can be configured to include trades in them, which might be a good idea because IB's Flex Query API is not very tolerant of multiple requests in succession.

On the other hand, maybe this increases the likelihood that they'll error out the query? Needs experimentation.

@jspahrsummers
Copy link
Member Author

This will likely be complicated by the fact that Activity queries seem to (generally) take much longer than Trades.

@jspahrsummers jspahrsummers transferred this issue from bankroll-py/bankroll Aug 29, 2019
@jspahrsummers jspahrsummers added the question Further information is requested label Aug 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Development

No branches or pull requests

1 participant