Alpaca-trade-api

Latest version: v3.2.0

Safety actively analyzes 629436 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 10

0.32

The joining of Polygon streams in v0.31 was broken because it was using the wrong character. This has been fixed in this version.

0.31

In this release, we replace the old NATS connection for Polygon streaming with their new websocket endpoint. This change should be largely invisible to users, but we expect that the websocket connection will be more stable and reliable than the NATS connection was. If you wish to change the endpoint that the Polygon websocket attempts to connect to, you may specify it in the environment variable `POLYGON_WS_URL`.

Breaking changes:
This release also changes the names of Polygon aggregate fields on the v2 endpoint from their short version to their long versions. This is done for the sake of consistency with the rest of the SDK. Please note that if you were using v2 Polygon aggregates before this release, you will need to update your code to account for the long names.

0.30

This update simply changes the Alpaca API version used by default from v1 to v2, as new Alpaca accounts now support v2 features. This preference can be overridden by setting the environment variable `APCA_API_VERSION` to `v1`.

0.29

- Add extended_hours flag to POST /orders
- Fix data API endpoint to always use v1

0.28

A user discovered that when getting recent aggregate data for companies that have not been traded yet, the result list can be empty and an error would be thrown. This corrects the error and instead returns an empty list.

0.27

This release introduces the ability to configure the version of the Alpaca API to target. This is currently primarily intended for users using Alpaca power accounts. It also includes a new historic_agg_v2() method for Polygon's API. The V2 endpoint reportedly does not experience some of the performance issues users have noticed with the V1 endpoint, so if your code has been having trouble with that, please try the new endpoint.

Page 8 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.