---
title: "US Equities Detailed Shares Outstanding"
method: GET
path: "/v1/data/us-equity-ref/shares-outst-detail"
tags: ["us-equity-ref-fundamentals"]
---

# US Equities Detailed Shares Outstanding

`GET /v1/data/us-equity-ref/shares-outst-detail`

The U.S. Equities Shares Outstanding (Detailed) dataset provides a granular, event-level history of shares outstanding for U.S. exchange-listed equity securities. It extends the basic shares outstanding dataset by exposing additional metadata and change attribution, enabling deeper analysis of share count dynamics over time. In addition to core fields such as algoseek SecId, ticker symbol, effective date, and shares outstanding, the detailed dataset includes the security name, the change in shares outstanding relative to the prior value, a unique event identifier for each update, the security’s listing date, and the current security status (e.g., active, in default, or inactive). The dataset is updated continuously throughout the trading day, providing timely visibility into newly reported or revised share count changes. It is designed to support valuation modeling, capitalization analysis, regulatory reporting, and research workflows that require event-level explainability and precise share count attribution.

 For more details, please refer to the dataset documentation: [US Equities Detailed Shares Outstanding  Guide](https://us-equity-reference-docs.s3.us-east-1.amazonaws.com/algoseek.US.Equity.Shares.Outstanding.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

- `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

- USEquitiesDetailedSharesOutstandingDataOut
  - `data` USEquitiesDetailedSharesOutstandingDataDetailsOut[], required
    - `SecId` integer, nullable — A unique identifier for a security
    - `Ticker` string, nullable — Symbol name
    - `ASID` integer, nullable — A unique identifier for a security
    - `CreatedDate` string, date, nullable — Trading date when SO event was created
    - `ChangedDate` string, date, nullable — Trading date and version number (_n suffix) when SO event was changed
    - `Revision` integer, nullable — Version of the algoseek event report file
    - `EffectiveDate` string, date, nullable — Effective date of SO value change
    - `Name` string, nullable — Company name
    - `SharesOutstanding` integer, nullable — New shares outstanding figure
    - `SharesOutstandingDiff` integer, nullable — Change of SO, comparing with the previous figure
    - `EventId` integer, nullable — Unique Event Identifier of SO event
    - `ListDate` string, date, nullable — Date of Listing
    - `Status` string, nullable — Security Status
  - `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)