<> API Reference

• Subscribe to Trade Events (SSE) is updated to include below fields
  • Added position_intent/expires_at fields under order field
  • Added swap_rate field

Multi-leg (Level 3) options are officially LIVE in our Trading API and dashboard 🎉

You can now trade advanced options trading strategies including: straddles, strangles, iron butterflies, iron condors, and various spreads (like credit, debit, and calendar).

These advanced strategies may help investors:

1. Capitalize on market volatility, range-bound price movements, and directional trends.
2. Increase efficiency by combining multiple options contracts into one single trade.
3. Improve risk management by ensuring all legs are executed simultaneously– shielding them from partial fills and unexpected market shifts.

And with multiple paper accounts, you can test various strategies at the same time before taking them live.

Start trading multi-leg options with Alpaca: https://bit.ly/3COa6Re

📔 Documentation

• Introduce an Multi-leg (Level 3) Options Trading Guide
• Learn about the differences between an iron condor and iron butterfly

<> API Reference

• Place Multi-leg Orders: Submit multi-leg orders via the POST /orders endpoint, where you’ll also find examples.
• Use Our SDKs: Get started quickly with alpacahq/alpaca-py or alpacahq/alpaca-trade-api-go .

Price band protection introduced to prevent trades from executing outside a predefined percentage range around an external reference price.

Order Validation Updates
Orders that would execute at an invalid price will be automatically canceled.

Reject Reasons Updates
Orders may now be canceled with the following reasons:

1. canceled due to reference price stale – Order was canceled because the reference price used for price band validation was outdated.
2. canceled due to price band protection. Index price: <index_price> Price band: <price_band>%, Rejected price: <maker_order_price> – Order was about to execute at a price exceeding the allowed range

• SSE comment message descriptions and examples are added to the documentation also added to the API reference
• A new action type (error) added for a few Trade API WebSocket streams documentation

<> API Reference

• A new id field has been added to all corporate action types in the response of the Corporate Actions endpoint.
• The ids filter has been added to the same endpoint that can be used to query corporate actions by ID. This filter is mutually exclusive to the other filters (e.g. symbols, types) and the number of IDs queried must be less than or equal to the limit.

Multi-leg (Level 3) Options are now available in Trading API and dashboard in Paper 🎉

With Level 3 options trading, you can trade multi-leg strategies like: straddles, strangles, iron butterflies, iron condors, and spreads to capitalize on specific market volatility, range-bound price movements, and directional trends.
This may help traders:

1. Increase efficiency by combining multiple options contracts into one single trade.
2. Enhance risk management by ensuring all parts of their strategy are executed simultaneously– protecting traders from partial fills and market movement.

📔 Documentation

• Introduce an Multi-leg (Level 3) Options Trading Guide
• Learn about the differences between an iron condor and iron butterfly

<> API Reference

• Place Multi-leg Orders: Submit multi-leg orders via the POST /orders endpoint, where you’ll also find examples.
• Use Our SDKs: Get started quickly with alpacahq/alpaca-py or alpacahq/alpaca-trade-api-go .

Added a sentence “ On all orders (regardless of commission type), the commission charged will be prorated on each execution if the order has multiple executions. For instance, if 10% of the order is filled on one execution then the commission on that execution will be 10% of the total commission.”

The old announcements endpoint has been deprecated in favour of the more recent corporate actions endpoint. The new endpoint offers more structured response (different schema for each corporate action type) and better overall data quality.

The version of the new endpoint has been increased from v1beta1 to v1. This means that we now promise backward compatibility guarantee for the endpoint: we will not introduce breaking changes. The previous v1beta1 version can still be used, so no migration is required if you've already been using the endpoint.

<> API Reference

Activities API

• The GET /activities response payload now includes a new optional field activity_sub_type. This field provides a more detailed classification, in addition to the existing activity_type field.
• A new entry_type, OPCA (Options Corporate Action), has been introduced to improve the classification and reporting of options corporate action activities.
• For further details, refer to the Activities API documentation:
  • Activities API - Trading
  • Activities API - Broker

Added a sentence “Please note: On orders to sell if the commission input will be more than the principal of the transaction then the principal amount of the transaction (net of SEC REG and FINRA TAF fees) will be charged as commission and not the amount specified in the order.”

📔 Documentation

You can follow the documentation in the Broker API Trading Page.