You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| get_barset(symbols, timeframe, limit, start=None, end=None, after=None, until=None) |`GET /bars/{timeframe}`| Barset with `limit` Bar objects for each of the the requested symbols. `timeframe` can be one of `minute`, `1Min`, `5Min`, `15Min`, `day` or `1D`. `minute` is an alias of `1Min`. Similarly, `day` is an alias of `1D`. `start`, `end`, `after`, and `until` need to be string format, which you can obtain with `pd.Timestamp().isoformat()``after` cannot be used with `start` and `until` cannot be used with `end`.|
322
-
| get_aggs(symbol, timespan, multiplier, _from, to)|`GET /aggs/ticker/{symbol}/range/{multiplier}/{timespan}/{from}/{to}`|`Aggs` entity. `multiplier` is the size of the timespan multiplier. `timespan` is the size of the time window, can be one of `minute`, `hour`, `day`, `week`, `month`, `quarter` or `year`. `_from` and `to` must be in `YYYY-MM-DD` format, e.g. `2020-01-15`.|
| get_portfolio_history(date_start=None, date_end=None, period=None, timeframe=None, extended_hours=None) |`GET /account/portfolio/history`| PortfolioHistory entity. PortfolioHistory.df can be used to get the results as a dataframe|
@@ -372,38 +368,21 @@ api.submit_order(
372
368
)
373
369
```
374
370
375
-
##### Using `get_barset()` (Deprecated. use `get_bars()` instead)
please note that if you are using limit, it is calculated from the end date. and if end date is not specified, "now" is used. <br>Take that under consideration when using start date with a limit.
391
-
392
371
---
393
372
394
373
#### Debugging
395
374
Websocket exceptions may occur during execution.
396
-
It will usually happen during the `consume()` method, which basically is the
375
+
It will usually happen during the `consume()` method, which basically is the
397
376
websocket steady-state.<br>
398
377
exceptions during the consume method may occur due to:
399
378
- server disconnections
400
379
- error while handling the response data
401
380
402
381
We handle the first issue by reconnecting the websocket every time there's a disconnection.
403
-
The second issue, is usually a user's code issue. To help you find it, we added a flag to the
382
+
The second issue, is usually a user's code issue. To help you find it, we added a flag to the
404
383
StreamConn object called `debug`. It is set to False by default, but you can turn it on to get a more
405
384
verbose logs when this exception happens.
406
-
Turn it on like so `StreamConn(debug=True)`
385
+
Turn it on like so `StreamConn(debug=True)`
407
386
408
387
## Logging
409
388
You should define a logger in your app in order to make sure you get all the messages from the different components.<br>
0 commit comments