Alpaca Markets APIs

3 APIs220 Endpoints1 Category

API Catalog(3 of 3)

Alpaca Market Data API

The Alpaca Market Data API provides real-time and historical market data for US equities, options, crypto, crypto perpetual futures, and foreign exchange. Endpoints cover historical bars, quotes, trades, and auctions for stocks, options chains and snapshots, crypto bars and orderbooks, forex rates, screeners for movers and most-actives, news articles, corporate actions, and company logos. Authentication uses APCA-API-KEY-ID and APCA-API-SECRET-KEY headers. Both production and sandbox endpoints are exposed.

45 endpoints

Alpaca Trading API

The Alpaca Trading API is the self-directed trading surface of the Alpaca platform, designed for individual developers and algorithmic traders running their own brokerage account. It exposes orders, positions, watchlists, account configurations, account activities, market calendar and clock, assets, options contracts, corporate actions, crypto funding wallets, and portfolio history. Authentication uses APCA-API-KEY-ID and APCA-API-SECRET-KEY headers, and live and paper environments are exposed at api.alpaca.markets and paper-api.alpaca.markets respectively. With 44 endpoints, this API is focused on trading, not on opening or managing customer accounts.

44 endpoints

Broker API

The Alpaca Broker API lets businesses open and manage brokerage accounts and offer stock, options, and crypto trading to their end users under their own brand. It covers the full account lifecycle including onboarding, KYC and CIP, ACH and bank relationship setup, funding wallets, journals between accounts, trading on behalf of accounts, watchlists, corporate actions, and rebalancing portfolios. The API uses HTTP basic authentication for server-to-server calls and exposes both production and sandbox endpoints. With 131 endpoints, it is the broadest of Alpaca's three APIs and is intended for fintechs building branded investing products.

Connect Your Agent

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.