Skip to main content
Alpaca is an officially supported broker integration in Anthid, providing access to both paper and live trading environments through the same platform interface used by other supported brokers. Anthid manages encrypted credential storage, broker connection setup, account routing, and platform integration layers so applications can connect Alpaca accounts without building a separate broker client stack.

​
Availability

Stability: Beta. The functionality documented on this page is implemented and routed end to end in both paper and live environments. The integration is usable in production and is still being hardened, so broker-specific behavior can change ahead of general availability.This integration carries no service level commitment. See Integration stability and Service levels.
Alpaca is currently available to all organizations. Support includes:
  • Paper trading accounts
  • Live trading accounts
  • Intent-based order submission
  • Real-time order updates
  • Risk and trading controls
  • Historical ledger storage

​
Supported Environments

Both environments can be connected within the same organization.

​
Supported functionality

The current intent integration supports:
  • Market orders
  • Limit orders
  • Stop orders
  • Stop-limit orders
  • DAY, GOOD_TILL_CANCEL, IMMEDIATE_OR_CANCEL, AT_OPEN, AT_CLOSE, and FILL_OR_KILL
  • Smart routing
Not yet supported:
  • Trailing stop orders are coming soon. Alpaca accepts them, but the intent schema carries no trail offset, so one cannot be expressed yet. An intent naming TrailingStop is refused at submission rather than sent on.
Position updates are not yet reported for Alpaca accounts. Order updates stream normally, and orders are recorded in the ledger as usual. Positions are not: the Alpaca integration does not yet report holdings back to Anthid, so an Alpaca account shows no positions through the platform, on the stream or in the ledger.Read positions from Alpaca directly until this note is removed. Lightspeed Connect reports positions today. See Positions.
For request shapes and exact enum values, see Supported Order Types, Supported Destinations, and Supported Time In Force.

​
Trading Accounts

Each Alpaca account connected to Anthid is represented as a Trading Account. Trading Accounts can be used with:
  • Intents
  • Orders
  • Positions
  • Controls
  • Streaming API
  • Historical ledger APIs
Applications interact with Trading Accounts rather than directly managing broker sessions.

​
Authentication

Alpaca credentials are managed through Anthid Trading Accounts. Applications never communicate directly with Alpaca APIs and do not need to manage broker authentication flows, credential storage, or platform account routing.

​
Support

For questions about broker connectivity, request formats, or platform behavior, contact support@anthid.com.