Top Related Projects
A JavaScript / TypeScript / Python / C# / PHP cryptocurrency trading API with support for more than 100 bitcoin/altcoin exchanges
Zipline, a Pythonic Algorithmic Trading Library
Download market data from Yahoo! Finance's API
Python wrapper for TA-Lib (http://ta-lib.org/).
Common financial technical indicators implemented in Pandas.
Lean Algorithmic Trading Engine by QuantConnect (Python, C#)
Quick Overview
Alpaca Trade API Python is a Python library for the Alpaca Commission-Free Trading API. It allows developers to programmatically trade stocks and ETFs, manage portfolios, and access market data. The library provides a simple and intuitive interface for interacting with the Alpaca API, making it easier to build automated trading systems and financial applications.
Pros
- Easy to use and well-documented API
- Supports both paper trading and live trading environments
- Provides real-time market data and historical data access
- Offers a wide range of order types and trading functionalities
Cons
- Limited to US markets only
- Requires API key authentication, which may be a barrier for beginners
- Some advanced features may require a paid subscription
- Potential for rate limiting on API calls
Code Examples
- Initializing the API client:
from alpaca.trading.client import TradingClient
trading_client = TradingClient('your-api-key', 'your-secret-key', paper=True)
- Placing a market order:
from alpaca.trading.requests import MarketOrderRequest
from alpaca.trading.enums import OrderSide, TimeInForce
order_details = MarketOrderRequest(
symbol="AAPL",
qty=10,
side=OrderSide.BUY,
time_in_force=TimeInForce.DAY
)
order = trading_client.submit_order(order_data=order_details)
- Getting account information:
account = trading_client.get_account()
print(f"Account ID: {account.id}")
print(f"Cash: ${account.cash}")
print(f"Buying Power: ${account.buying_power}")
- Fetching historical bar data:
from alpaca.data.historical import StockHistoricalDataClient
from alpaca.data.requests import StockBarsRequest
from alpaca.data.timeframe import TimeFrame
data_client = StockHistoricalDataClient('your-api-key', 'your-secret-key')
request_params = StockBarsRequest(
symbol_or_symbols=["AAPL", "MSFT"],
timeframe=TimeFrame.Day,
start="2023-01-01"
)
bars = data_client.get_stock_bars(request_params)
for symbol, bar_data in bars.items():
print(f"Data for {symbol}:")
for bar in bar_data:
print(f"Date: {bar.timestamp}, Close: {bar.close}")
Getting Started
-
Install the library:
pip install alpaca-trade-api
-
Set up your Alpaca account and obtain API keys from the Alpaca dashboard.
-
Initialize the API client:
from alpaca.trading.client import TradingClient trading_client = TradingClient('your-api-key', 'your-secret-key', paper=True)
-
Start trading or accessing market data using the available methods in the
trading_client
object.
Competitor Comparisons
A JavaScript / TypeScript / Python / C# / PHP cryptocurrency trading API with support for more than 100 bitcoin/altcoin exchanges
Pros of ccxt
- Supports a wide range of cryptocurrency exchanges (180+)
- Provides a unified API for trading across multiple platforms
- Active community and frequent updates
Cons of ccxt
- Steeper learning curve due to its extensive features
- May include unnecessary functionality for users focused on a single exchange
- Potential performance overhead from supporting multiple exchanges
Code Comparison
alpaca-trade-api-python:
from alpaca_trade_api import REST
api = REST()
account = api.get_account()
print(f"Account balance: ${account.cash}")
ccxt:
import ccxt
exchange = ccxt.binance()
balance = exchange.fetch_balance()
print(f"Account balance: ${balance['total']['USDT']}")
Both libraries provide straightforward methods to interact with trading platforms, but ccxt requires specifying the exchange explicitly. alpaca-trade-api-python is more focused on the Alpaca platform, while ccxt offers flexibility across multiple exchanges.
Zipline, a Pythonic Algorithmic Trading Library
Pros of Zipline
- Comprehensive backtesting framework with built-in data management
- Extensive documentation and community support
- Integrates well with other Quantopian tools and libraries
Cons of Zipline
- Steeper learning curve for beginners
- Less focus on live trading compared to Alpaca Trade API
- Development has slowed since Quantopian's acquisition
Code Comparison
Zipline example:
from zipline.api import order, record, symbol
def initialize(context):
context.asset = symbol('AAPL')
def handle_data(context, data):
order(context.asset, 10)
record(AAPL=data.current(context.asset, 'price'))
Alpaca Trade API example:
import alpaca_trade_api as tradeapi
api = tradeapi.REST()
api.submit_order(
symbol='AAPL',
qty=10,
side='buy',
type='market',
time_in_force='gtc'
)
Zipline focuses on backtesting and strategy development, offering a more comprehensive framework for algorithmic trading. It provides built-in data management and integrates well with other Quantopian tools. However, it has a steeper learning curve and less emphasis on live trading.
Alpaca Trade API, on the other hand, is more straightforward for beginners and primarily designed for live trading. It offers a simpler API for executing trades and managing positions but lacks the extensive backtesting capabilities of Zipline.
Download market data from Yahoo! Finance's API
Pros of yfinance
- Free and easy to use without requiring an account or API key
- Provides access to a wide range of financial data, including stocks, options, and cryptocurrencies
- Offers historical data with adjustable time ranges and intervals
Cons of yfinance
- Data accuracy and reliability can be inconsistent, especially for real-time data
- Limited support for advanced trading features and order placement
- May face potential legal issues due to web scraping Yahoo Finance
Code Comparison
yfinance:
import yfinance as yf
ticker = yf.Ticker("AAPL")
hist = ticker.history(period="1mo")
print(hist)
alpaca-trade-api-python:
from alpaca_trade_api.rest import REST
api = REST()
barset = api.get_barset('AAPL', 'day', limit=30)
aapl_bars = barset['AAPL']
print(aapl_bars)
Both libraries allow fetching historical data, but yfinance is simpler to set up and use, while alpaca-trade-api-python requires authentication and offers more advanced trading capabilities.
Python wrapper for TA-Lib (http://ta-lib.org/).
Pros of ta-lib-python
- Extensive library of technical analysis functions
- Well-established and widely used in the financial industry
- Optimized C implementations for improved performance
Cons of ta-lib-python
- Requires separate installation of TA-Lib C library
- Limited to technical analysis functions only
- Steeper learning curve for beginners
Code Comparison
ta-lib-python:
import talib
import numpy as np
close_prices = np.random.random(100)
sma = talib.SMA(close_prices, timeperiod=20)
rsi = talib.RSI(close_prices, timeperiod=14)
alpaca-trade-api-python:
from alpaca_trade_api.rest import REST
api = REST()
account = api.get_account()
positions = api.list_positions()
order = api.submit_order(symbol='AAPL', qty=1, side='buy', type='market', time_in_force='gtc')
The ta-lib-python library focuses on providing a wide range of technical analysis functions, while alpaca-trade-api-python is designed for interacting with the Alpaca trading platform, offering features like account management, order placement, and market data retrieval. ta-lib-python is more specialized and computationally efficient for technical analysis tasks, whereas alpaca-trade-api-python provides a broader set of tools for algorithmic trading and portfolio management.
Common financial technical indicators implemented in Pandas.
Pros of finta
- Focused specifically on financial technical indicators
- Lightweight and easy to integrate into existing projects
- Supports a wide range of technical indicators
Cons of finta
- Limited to technical analysis, no trading functionality
- Less active development and community support
- May require additional libraries for data retrieval and manipulation
Code Comparison
finta:
from finta import TA
import pandas as pd
df = pd.DataFrame(your_data)
rsi = TA.RSI(df)
macd = TA.MACD(df)
alpaca-trade-api-python:
from alpaca_trade_api.rest import REST
import pandas as pd
api = REST()
df = api.get_barset('AAPL', 'day', limit=100).df['AAPL']
# Additional processing required for technical indicators
finta is more focused on calculating technical indicators, while alpaca-trade-api-python provides a broader range of trading-related functionalities, including data retrieval and order execution. finta requires you to provide your own data, whereas alpaca-trade-api-python can fetch market data directly. For technical analysis, finta offers a more straightforward approach, but alpaca-trade-api-python provides a more comprehensive trading ecosystem.
Lean Algorithmic Trading Engine by QuantConnect (Python, C#)
Pros of Lean
- Comprehensive algorithmic trading framework with backtesting and live trading capabilities
- Supports multiple asset classes and markets
- Extensive documentation and community support
Cons of Lean
- Steeper learning curve due to its complexity
- Requires more setup and configuration compared to simpler APIs
- May be overkill for basic trading strategies or simple API interactions
Code Comparison
Lean (C#):
public class SimpleMovingAverageAlgorithm : QCAlgorithm
{
public override void Initialize()
{
SetStartDate(2013, 10, 07);
SetEndDate(2013, 10, 11);
SetCash(100000);
AddEquity("SPY", Resolution.Minute);
}
}
Alpaca Trade API Python:
api = tradeapi.REST('API_KEY', 'API_SECRET', base_url='https://paper-api.alpaca.markets')
account = api.get_account()
api.submit_order(
symbol='SPY',
qty=100,
side='buy',
type='market',
time_in_force='gtc'
)
The Lean framework provides a more structured approach for developing complex trading algorithms, while the Alpaca Trade API offers a simpler interface for basic trading operations. Lean is better suited for comprehensive strategy development and backtesting, whereas Alpaca Trade API is more straightforward for quick implementations and API interactions.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
Deprecation Notice
A new python SDK, Alpaca-py, is available. This SDK will be the primary python SDK starting in 2023. We recommend moving over your code to use the new SDK. Keep in mind, we will be maintaining this repo as usual until the end of 2022.
alpaca-trade-api-python
alpaca-trade-api-python
is a python library for the Alpaca Commission Free Trading API.
It allows rapid trading algo development easily, with support for
both REST and streaming data interfaces. For details of each API behavior,
please see the online API document.
Note that this package supports only python version 3.7 and above.
Install
We support python>=3.7. If you want to work with python 3.6, please note that these package dropped support for python <3.7 for the following versions:
pandas >= 1.2.0
numpy >= 1.20.0
scipy >= 1.6.0
The solution - manually install these packages before installing alpaca-trade-api. e.g:
pip install pandas==1.1.5 numpy==1.19.4 scipy==1.5.4
Also note that we do not limit the version of the websockets library, but we advise using
websockets>=9.0
Installing using pip
$ pip3 install alpaca-trade-api
API Keys
To use this package you first need to obtain an API key. Go here to signup
Services
These services are provided by Alpaca:
The free services are limited, please check the docs to see the differences between paid/free services.
Alpaca Environment Variables
The Alpaca SDK will check the environment for a number of variables that can be used rather than hard-coding these into your scripts.
Alternatively you could pass the credentials directly to the SDK instances.
Environment | default | Description |
---|---|---|
APCA_API_KEY_ID=<key_id> | Your API Key | |
APCA_API_SECRET_KEY=<secret_key> | Your API Secret Key | |
APCA_API_BASE_URL=url | https://api.alpaca.markets (for live) | Specify the URL for API calls, Default is live, you must specify https://paper-api.alpaca.markets to switch to paper endpoint! |
APCA_API_DATA_URL=url | https://data.alpaca.markets | Endpoint for data API |
APCA_RETRY_MAX=3 | 3 | The number of subsequent API calls to retry on timeouts |
APCA_RETRY_WAIT=3 | 3 | seconds to wait between each retry attempt |
APCA_RETRY_CODES=429,504 | 429,504 | comma-separated HTTP status code for which retry is attempted |
DATA_PROXY_WS | When using the alpaca-proxy-agent you need to set this environment variable as described |
Working with Data
Historic Data
You could get one of these historic data types:
- Bars
- Quotes
- Trades
You now have 2 pythonic ways to retrieve historical data.
One using the traditional rest module and the other is to use the experimental asyncio module added lately.
Let's have a look at both:
The first thing to understand is the new data polling mechanism. You could query up to 10000 items, and the API is using a pagination mechanism to provide you with the data.
You now have 2 options:
- Working with data as it is received with a generator. (meaning it's faster but you need to process each item alone)
- Wait for the entire data to be received, and then work with it as a list or dataframe. We provide you with both options to choose from.
Bars
option 1: wait for the data
from alpaca_trade_api.rest import REST, TimeFrame
api = REST()
api.get_bars("AAPL", TimeFrame.Hour, "2021-06-08", "2021-06-08", adjustment='raw').df
open high low close volume
timestamp
2021-06-08 08:00:00+00:00 126.100 126.3000 125.9600 126.3000 42107
2021-06-08 09:00:00+00:00 126.270 126.4000 126.2200 126.3800 21095
2021-06-08 10:00:00+00:00 126.380 126.6000 125.8400 126.4900 54743
2021-06-08 11:00:00+00:00 126.440 126.8700 126.4000 126.8500 206460
2021-06-08 12:00:00+00:00 126.821 126.9500 126.7000 126.9300 385164
2021-06-08 13:00:00+00:00 126.920 128.4600 126.4485 127.0250 18407398
2021-06-08 14:00:00+00:00 127.020 127.6400 126.7800 127.1350 13446961
2021-06-08 15:00:00+00:00 127.140 127.4700 126.2101 126.6100 10444099
2021-06-08 16:00:00+00:00 126.610 126.8400 126.5300 126.8250 5289556
2021-06-08 17:00:00+00:00 126.820 126.9300 126.4300 126.7072 4813459
2021-06-08 18:00:00+00:00 126.709 127.3183 126.6700 127.2850 5338455
2021-06-08 19:00:00+00:00 127.290 127.4200 126.6800 126.7400 9817083
2021-06-08 20:00:00+00:00 126.740 126.8500 126.5400 126.6600 5525520
2021-06-08 21:00:00+00:00 126.690 126.8500 126.6500 126.6600 156333
2021-06-08 22:00:00+00:00 126.690 126.7400 126.6600 126.7300 49252
2021-06-08 23:00:00+00:00 126.725 126.7600 126.6400 126.6400 41430
option 2: iterate over bars
def process_bar(bar):
# process bar
print(bar)
bar_iter = api.get_bars_iter("AAPL", TimeFrame.Hour, "2021-06-08", "2021-06-08", adjustment='raw')
for bar in bar_iter:
process_bar(bar)
Alternatively, you can decide on your custom timeframes by using the TimeFrame constructor:
from alpaca_trade_api.rest import REST, TimeFrame, TimeFrameUnit
api = REST()
api.get_bars("AAPL", TimeFrame(45, TimeFrameUnit.Minute), "2021-06-08", "2021-06-08", adjustment='raw').df
open high low close volume trade_count vwap
timestamp
2021-06-08 07:30:00+00:00 126.1000 126.1600 125.9600 126.0600 20951 304 126.049447
2021-06-08 08:15:00+00:00 126.0500 126.3000 126.0500 126.3000 21181 349 126.231904
2021-06-08 09:00:00+00:00 126.2700 126.3200 126.2200 126.2800 15955 308 126.284120
2021-06-08 09:45:00+00:00 126.2900 126.4000 125.9000 125.9000 30179 582 126.196877
2021-06-08 10:30:00+00:00 125.9000 126.7500 125.8400 126.7500 105380 1376 126.530863
2021-06-08 11:15:00+00:00 126.7300 126.8500 126.5600 126.8300 129721 1760 126.738041
2021-06-08 12:00:00+00:00 126.4101 126.9500 126.3999 126.8300 418107 3615 126.771889
2021-06-08 12:45:00+00:00 126.8500 126.9400 126.6000 126.6200 428614 5526 126.802825
2021-06-08 13:30:00+00:00 126.6200 128.4600 126.4485 127.4150 23065023 171263 127.425797
2021-06-08 14:15:00+00:00 127.4177 127.6400 126.9300 127.1350 8535068 65753 127.342337
2021-06-08 15:00:00+00:00 127.1400 127.4700 126.2101 126.7101 8447696 64616 126.789316
2021-06-08 15:45:00+00:00 126.7200 126.8200 126.5300 126.6788 5084147 38366 126.712110
2021-06-08 16:30:00+00:00 126.6799 126.8400 126.5950 126.5950 3205870 26614 126.718837
2021-06-08 17:15:00+00:00 126.5950 126.9300 126.4300 126.7010 3908283 31922 126.665727
2021-06-08 18:00:00+00:00 126.7072 127.0900 126.6700 127.0600 3923056 29114 126.939887
2021-06-08 18:45:00+00:00 127.0500 127.4200 127.0000 127.0050 5051682 38235 127.214157
2021-06-08 19:30:00+00:00 127.0150 127.0782 126.6800 126.7800 11665598 47146 126.813182
2021-06-08 20:15:00+00:00 126.7700 126.7900 126.5400 126.6600 83725 1973 126.679259
2021-06-08 21:00:00+00:00 126.6900 126.8500 126.6700 126.7200 145153 769 126.746457
2021-06-08 21:45:00+00:00 126.7000 126.7400 126.6500 126.7100 38455 406 126.699544
2021-06-08 22:30:00+00:00 126.7100 126.7600 126.6700 126.7100 30822 222 126.713892
2021-06-08 23:15:00+00:00 126.7200 126.7600 126.6400 126.6400 32585 340 126.704131
Quotes
option 1: wait for the data
from alpaca_trade_api.rest import REST
api = REST()
api.get_quotes("AAPL", "2021-06-08", "2021-06-08", limit=10).df
ask_exchange ask_price ask_size bid_exchange bid_price bid_size conditions
timestamp
2021-06-08 08:00:00.070928640+00:00 P 143.00 1 0.00 0 [Y]
2021-06-08 08:00:00.070929408+00:00 P 143.00 1 P 102.51 1 [R]
2021-06-08 08:00:00.070976768+00:00 P 143.00 1 P 116.50 1 [R]
2021-06-08 08:00:00.070978816+00:00 P 143.00 1 P 118.18 1 [R]
2021-06-08 08:00:00.071020288+00:00 P 143.00 1 P 120.00 1 [R]
2021-06-08 08:00:00.071020544+00:00 P 134.18 1 P 120.00 1 [R]
2021-06-08 08:00:00.071021312+00:00 P 134.18 1 P 123.36 1 [R]
2021-06-08 08:00:00.071209984+00:00 P 131.11 1 P 123.36 1 [R]
2021-06-08 08:00:00.071248640+00:00 P 130.13 1 P 123.36 1 [R]
2021-06-08 08:00:00.071286016+00:00 P 129.80 1 P 123.36 1 [R]
option 2: iterate over quotes
def process_quote(quote):
# process quote
print(quote)
quote_iter = api.get_quotes_iter("AAPL", "2021-06-08", "2021-06-08", limit=10)
for quote in quote_iter:
process_quote(quote)
Trades
option 1: wait for the data
from alpaca_trade_api.rest import REST
api = REST()
api.get_trades("AAPL", "2021-06-08", "2021-06-08", limit=10).df
exchange price size conditions id tape
timestamp
2021-06-08 08:00:00.069956608+00:00 P 126.10 179 [@, T] 1 C
2021-06-08 08:00:00.207859+00:00 K 125.97 1 [@, T, I] 1 C
2021-06-08 08:00:00.207859+00:00 K 125.97 12 [@, T, I] 2 C
2021-06-08 08:00:00.207859+00:00 K 125.97 4 [@, T, I] 3 C
2021-06-08 08:00:00.207859+00:00 K 125.97 4 [@, T, I] 4 C
2021-06-08 08:00:00.207859+00:00 K 125.97 8 [@, T, I] 5 C
2021-06-08 08:00:00.207859+00:00 K 125.97 1 [@, T, I] 6 C
2021-06-08 08:00:00.207859+00:00 K 126.00 30 [@, T, I] 7 C
2021-06-08 08:00:00.207859+00:00 K 126.00 10 [@, T, I] 8 C
2021-06-08 08:00:00.207859+00:00 K 125.97 70 [@, T, I] 9 C
option 2: iterate over trades
def process_trade(trade):
# process trade
print(trade)
trades_iter = api.get_trades_iter("AAPL", "2021-06-08", "2021-06-08", limit=10)
for trade in trades_iter:
process_trade(trade)
Asyncio Rest module
The rest_async.py
module now provides an asyncion approach to retrieving the historic data.
This module is, and thus may have expansions in the near future to support more endpoints.
It provides a much faster way to retrieve the historic data for multiple symbols.
Under the hood we use the aiohttp library.
We provide a code sample to get you started with this new approach and it is located here.
Follow along with the example code to learn more, and utilize it for your own needs.
Live Stream Market Data
There are 2 streams available as described here.
The free plan is using the iex
stream, while the paid subscription is using the sip
stream.
You can subscribe to bars, trades, quotes, and trade updates for your account as well. Under the example folder you can find different code samples to achieve different goals.
Here in this basic example, We use the Stream class under alpaca_trade_api.stream
for API V2 to subscribe to trade
updates for AAPL and quote updates for IBM.
from alpaca_trade_api.common import URL
from alpaca_trade_api.stream import Stream
async def trade_callback(t):
print('trade', t)
async def quote_callback(q):
print('quote', q)
# Initiate Class Instance
stream = Stream(<ALPACA_API_KEY>,
<ALPACA_SECRET_KEY>,
base_url=URL('https://paper-api.alpaca.markets'),
data_feed='iex') # <- replace to 'sip' if you have PRO subscription
# subscribing to event
stream.subscribe_trades(trade_callback, 'AAPL')
stream.subscribe_quotes(quote_callback, 'IBM')
stream.run()
Websockets Config For Live Data
Under the hood our SDK uses the Websockets library to handle
our websocket connections. Since different environments can have wildly differing requirements for resources we allow you
to pass your own config options to the websockets lib via the websocket_params
kwarg found on the Stream class.
ie:
# Initiate Class Instance
stream = Stream(<ALPACA_API_KEY>,
<ALPACA_SECRET_KEY>,
base_url=URL('https://paper-api.alpaca.markets'),
data_feed='iex', # <- replace to 'sip' if you have PRO subscription
websocket_params = {'ping_interval': 5}, #here we set ping_interval to 5 seconds
)
If you're curious this link to their docs shows the values that websockets uses by default as well as any parameters they allow changing. Additionally, if you don't specify any we set the following defaults on top of the ones the websockets library uses:
{
"ping_interval": 10,
"ping_timeout": 180,
"max_queue": 1024,
}
Account & Portfolio Management
The HTTP API document is located at https://docs.alpaca.markets/
API Version
API Version now defaults to 'v2', however, if you still have a 'v1' account, you may need to specify api_version='v1' to properly use the API until you migrate.
Authentication
The Alpaca API requires API key ID and secret key, which you can obtain from the
web console after you sign in. You can pass key_id
and secret_key
to the initializers of
REST
or Stream
as arguments, or set up environment variables as
outlined below.
REST
The REST
class is the entry point for the API request. The instance of this
class provides all REST API calls such as account, orders, positions,
and bars.
Each returned object is wrapped by a subclass of the Entity
class (or a list of it).
This helper class provides property access (the "dot notation") to the
json object, backed by the original object stored in the _raw
field.
It also converts certain types to the appropriate python object.
import alpaca_trade_api as tradeapi
api = tradeapi.REST()
account = api.get_account()
account.status
=> 'ACTIVE'
The Entity
class also converts the timestamp string field to a pandas.Timestamp
object. Its _raw
property returns the original raw primitive data unmarshaled
from the response JSON text.
Please note that the API is throttled, currently 200 requests per minute, per account. If your client exceeds this number, a 429 Too many requests status will be returned and this library will retry according to the retry environment variables as configured.
If the retries are exceeded, or other API error is returned, alpaca_trade_api.rest.APIError
is raised.
You can access the following information through this object.
- the API error code:
.code
property - the API error message:
str(error)
- the original request object:
.request
property - the original response object:
.response
property - the HTTP status code:
.status_code
property
API REST Methods
Rest Method | End Point | Result |
---|---|---|
get_account() | GET /account and | Account entity. |
get_order_by_client_order_id(client_order_id) | GET /orders with client_order_id | Order entity. |
list_orders(status=None, limit=None, after=None, until=None, direction=None, params=None,nested=None, symbols=None, side=None) | GET /orders | list of Order entities. after and until need to be string format, which you can obtain by pd.Timestamp().isoformat() |
submit_order(symbol, qty=None, side="buy", type="market", time_in_force="day", limit_price=None, stop_price=None, client_order_id=None, order_class=None, take_profit=None, stop_loss=None, trail_price=None, trail_percent=None, notional=None) | POST /orders | Order entity. |
get_order(order_id) | GET /orders/{order_id} | Order entity. |
cancel_order(order_id) | DELETE /orders/{order_id} | |
cancel_all_orders() | DELETE /orders | |
list_positions() | GET /positions | list of Position entities |
get_position(symbol) | GET /positions/{symbol} | Position entity. |
list_assets(status=None, asset_class=None) | GET /assets | list of Asset entities |
get_asset(symbol) | GET /assets/{symbol} | Asset entity |
get_clock() | GET /clock | Clock entity |
get_calendar(start=None, end=None) | GET /calendar | Calendar entity |
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 |
Rest Examples
Please see the examples/
folder for some example scripts that make use of this API
Using submit_order()
Below is an example of submitting a bracket order.
api.submit_order(
symbol='SPY',
side='buy',
type='market',
qty='100',
time_in_force='day',
order_class='bracket',
take_profit=dict(
limit_price='305.0',
),
stop_loss=dict(
stop_price='295.5',
limit_price='295.5',
)
)
For simple orders with type='market'
and time_in_force='day'
, you can pass a fractional amount (qty
) or a notional
amount (but not both). For instance, if the current market price for SPY is $300, the following calls are equivalent:
api.submit_order(
symbol='SPY',
qty=1.5, # fractional shares
side='buy',
type='market',
time_in_force='day',
)
api.submit_order(
symbol='SPY',
notional=450, # notional value of 1.5 shares of SPY at $300
side='buy',
type='market',
time_in_force='day',
)
Logging
You should define a logger in your app in order to make sure you get all the messages from the different components.
It will help you debug, and make sure you don't miss issues when they occur.
The simplest way to define a logger, if you have no experience with the python logger - will be something like this:
import logging
logging.basicConfig(format='%(asctime)s %(message)s', level=logging.INFO)
Websocket best practices
Under the examples folder you could find several examples to do the following:
- Different subscriptions(channels) usage with the alpaca streams
- pause / resume connection
- change subscriptions/channels of existing connection
- ws disconnections handler (make sure we reconnect when the internal mechanism fails)
Running Multiple Strategies
The base version of this library only allows running a single algorithm due to Alpaca's limit of one websocket connection per account. For those looking to run multiple strategies, there is alpaca-proxy-agent project.
The steps to execute this are:
- Run the Alpaca Proxy Agent as described in the project's README
- Define a new environment variable:
DATA_PROXY_WS
set to the address of the proxy agent. (e.g:DATA_PROXY_WS=ws://127.0.0.1:8765
) - If you are using the Alpaca data stream, make sure to initiate the Stream object with the container's url:
data_url='http://127.0.0.1:8765'
- Execute your algorithm. It will connect to the Alpaca servers through the proxy agent, allowing you to execute multiple strategies
Raw Data vs Entity Data
By default the data returned from the api or streamed via Stream is wrapped with an Entity object for ease of use. Some users may prefer working with vanilla python objects (lists, dicts, ...). You have 2 options to get the raw data:
- Each Entity object as a
_raw
property that extract the raw data from the object. - If you only want to work with raw data, and avoid casting to Entity (which may take more time, casting back and forth) you could pass
raw_data
argument toRest()
object or theStream()
object.
Support and Contribution
For technical issues particular to this module, please report the issue on this GitHub repository. Any API issues can be reported through Alpaca's customer support.
New features, as well as bug fixes, by sending a pull request is always welcomed.
Top Related Projects
A JavaScript / TypeScript / Python / C# / PHP cryptocurrency trading API with support for more than 100 bitcoin/altcoin exchanges
Zipline, a Pythonic Algorithmic Trading Library
Download market data from Yahoo! Finance's API
Python wrapper for TA-Lib (http://ta-lib.org/).
Common financial technical indicators implemented in Pandas.
Lean Algorithmic Trading Engine by QuantConnect (Python, C#)
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot