Historical trades

get

https://data.alpaca.markets/v1beta1/options/trades

The historical option trades API provides trade data for a list of contract symbols between the specified dates.

The returned results are sorted by symbol first then by trade timestamp. This means that you are likely to see only one symbol in your first response if there are enough trades for that symbol to hit the limit you requested.

In these situations, if you keep requesting again with the next_page_token from the previous response, you will eventually reach the other symbols if any trades were found for them.

Query Params

symbols

string

required

A comma-separated list of contract symbols with a limit of 100.

start

date-time

The inclusive start of the interval. Format: RFC-3339 or YYYY-MM-DD. Default: the beginning of the current day, but at least 15 minutes ago if the user doesn't have real-time access for the feed.

end

date-time

The inclusive end of the interval. Format: RFC-3339 or YYYY-MM-DD. Default: the current time if the user has a real-time access for the feed, otherwise 15 minutes before the current time.

limit

integer

1 to 10000

Defaults to 1000

The maximum number of data points to return in the response page. The API may return less, even if there are more available data points in the requested interval. Always check the next_page_token for more pages. The limit applies to the total number of data points, not per symbol!

page_token

string

The pagination token from which to continue. The value to pass here is returned in specific requests when more data is available, usually because of a response result limit.

sort

string

enum

Defaults to asc

Sort data in ascending or descending order.

Allowed:

Responses

401

Authentication headers are missing or invalid. Make sure you authenticate your request with a valid API key.

403

The requested resource is forbidden.

500

Internal server error. We recommend retrying these later. If the issue persists, please contact us on Slack or on the Community Forum.

200OK

400One of the request parameters is invalid. See the returned message for details.

429Too many requests. You hit the rate limit. Use the X-RateLimit-... response headers to make sure you're under the rate limit.