---
title: "US Equities Daily SSR Circuit Breakers"
method: GET
path: "/v1/data/us-equity-ref/ssr-circ-break"
tags: ["us-equity-ref-market-events"]
---

# US Equities Daily SSR Circuit Breakers

`GET /v1/data/us-equity-ref/ssr-circ-break`

The U.S. Equities Daily SSR Circuit Breakers dataset provides daily reference information on U.S. equity securities subject to the SEC Short Sale Rule (SSR), also known as Regulation SHO Rule 201. The SSR is triggered when a security experiences a significant intraday price decline (-10%), after which short sale executions are subject to price test restrictions. Once triggered, the rule restricts short sales to prices above the current National Best Bid (NBB) for the remainder of the trading day and the following trading day. This dataset identifies securities for which the SSR circuit breaker was in effect, enabling users to account for regulatory trading constraints in execution logic, compliance monitoring, and historical analysis. Data is published on a daily basis and is designed to support institutional trading systems, risk controls, and post-trade analysis involving short sale activity.

 For more details, please refer to the dataset documentation: [US Equities Daily SSR Circuit Breakers Guide](https://us-equity-reference-docs.s3.us-east-1.amazonaws.com/US.Equity.SSR.Circuit.Breakers.pdf).

<details>
<summary>**Advanced Filtering**</summary>

You can provide one or multiple filter expressions based on the dataset's columns to narrow down the results. For example, `StartDate.gt=2023-01-01&StartDate.lt=2023-12-31`, `Ticker=AAPL`. 

Please refer to the <a href="https://algoseek.com/docs/rest-api/tutorial/advanced-filtering">Advanced Filtering Guide</a> for the extensive reference.
</details>

## Query parameters

- `period` string, nullable — A string representing the time period for which to retrieve data. The format and accepted values depend on the dataset. If not provided, data for all available periods will be returned.
- `sort` string, nullable — Sorting criteria for the results. Provide a column name with optional prefix '+' for ascending order, or prefix with '-' for descending order. Multiple sorting fields may be supported depending on the dataset. If sort prefix is not provided, the ascending order is applied.
- `columns` string, nullable — A comma-separated list of columns to include in the response. Use this parameter to select only specific fields from the dataset. If not provided, all available columns will be returned.
- `offset` integer — Number of records to skip before returning results. To be used with the `limit` parameter for pagination. If not provided, defaults to 0.
- `limit` integer — Maximum number of records to return. Default and maximum values depend on the response format; see `format_limits` in the schema for details.
- `response_format` 'json' | 'csv' | 'csv_gzip' — Note the lowercase which is used for the consistency with other projects and tools

## Response `200`

JSON, CSV file, or gzip-compressed CSV file, depending on the value of `response_format` query parameter

- USEquitiesDailySSRCircuitBreakersDataOut
  - `data` USEquitiesDailySSRCircuitBreakersDataDetailsOut[], required
    - `TradeDate` string, date, nullable — The trading date
    - `TriggerTime` string, date-time, nullable — Time (EST) when Short Sale Rule is triggered with a second resolution
    - `SecId` integer, nullable — A unique identifier for a security
    - `ASID` integer, nullable — A unique identifier for a security
    - `Ticker` string, nullable — Symbol name
    - `Name` string, nullable — Security name
    - `PrimaryExchange` string, nullable — Primary listing exchange on the TradeDate
  - `pagination` PaginationDetailsOut, required
    - `offset` integer — The number of records skipped to fetch the current page
    - `limit` integer, required — The maximum number of records in the current page
    - `next_offset` integer, nullable — The number of records to skip to fetch the next page

## Other responses

- `403` — Forbidden
- `422` — Validation Error
- `429` — Request rejected because the identity or team exceeded a configured monthly or per-minute usage quota. When available, the response includes rate-limit headers describing the current quota.

---

[API](https://skmtc.net/algoseek/apis/datasets-api.md) · [All operations](https://skmtc.net/algoseek/apis/datasets-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/algoseek/datasets-api/revisions/1c983de099e2/schema)