Recent stock splits

GET/api/company/recent-stock-splits

Cross-company feed of recent stock splits across the entire SEC EDGAR universe, ordered by split date descending. Each entry attaches the company's primary ticker and name. Sourced from the same XBRL footnote disclosures as /api/company/stock-splits — see that endpoint for data-source details and caveats.

Use this to monitor corporate-action activity at the market level (e.g. screening for upcoming split-driven trades, surfacing reverse-split candidates that signal listing-compliance pressure).

Notes

Lookback window is configurable via days (default 90, max 365). The window applies to the split date itself, not the disclosure date.
firstDisclosedAt lag. XBRL splits are tagged in the next 10-K/10-Q after the event, so very recent splits may not yet appear here. A split executed today typically surfaces within 30-90 days. For real-time corporate-action use cases, pair with a dedicated corporate-actions feed.
Reverse splits dominate the feed. ~1,300 of the ~2,500 covered companies do reverse splits (often nano/micro-caps maintaining exchange listing requirements), versus ~1,200 doing forward splits. Filter by type client-side if you want only forwards.
Noop disclosures excluded. Rows with ratio = 1 (informational disclosures with no actual share-count change) are filtered out.

Get API key Try it live in the API explorer

Query parameters

days integer optional min 1 · max 365 · default 90

Lookback window in days, applied to the split date. Default 90.

Example: 90
page integer optional min 1 · max 1000 · default 1

Page number (1-indexed)

Example: 1
pageSize integer optional min 1 · max 100 · default 20

Number of results per page

Example: 20

Example request

curl 'https://api.stockfit.io/v1/api/company/recent-stock-splits?days=90&page=1&pageSize=20' \
  -H 'Authorization: Bearer YOUR_API_TOKEN'

Responses

200 OK

Paginated list of recent stock splits, newest first.

Response schema

page integer
pageSize integer
totalPages integer
totalResults integer
data array of object
array of:
- symbol string | null
  The company's primary ticker symbol. Null if the company has no listed ticker (rare — typically delisted issuers still filing with the SEC).
- name string | null
  Company name as registered with the SEC.
- cik integer
  SEC Central Index Key (always present, even when `symbol` is null).
- date string (date)
  The split date as tagged in the XBRL footnote (typically the ex-date or payable date). Format YYYY-MM-DD.
- ratio number
  The conversion ratio. `> 1` for forward splits (e.g. `3` = 3-for-1), `< 1` for reverse splits (e.g. `0.05` = 1-for-20). Compute post-split share count as `preSplit × ratio`.
- type string (enum)
  Stock split direction, derived from the split `ratio`: | Value | Meaning | |-------|---------| | `forward` | `ratio > 1`: share count increases, per-share price decreases. Typical of large-caps managing share price after a long run-up. | | `reverse` | `ratio < 1`: share count decreases, per-share price increases. Often used by small-caps to maintain exchange listing requirements (e.g. NASDAQ minimum bid price). |
  Allowed values: forward, reverse
- accession string
  SEC accession number of the filing where this split was first disclosed in XBRL.
- firstDisclosedAt string (date)
  SEC acceptance date (YYYY-MM-DD) of the filing referenced by `accession`. Lags the split date by weeks to months.

Example response

{
  "page": 1,
  "pageSize": 20,
  "totalPages": 7,
  "totalResults": 131,
  "data": [
    {
      "symbol": "TSLA",
      "name": "Tesla, Inc.",
      "cik": 1318605,
      "date": "2022-08-05",
      "ratio": 3,
      "type": "forward",
      "accession": "0000950170-22-019867",
      "firstDisclosedAt": "2022-10-24"
    },
    {
      "symbol": "GOOGL",
      "name": "Alphabet Inc.",
      "cik": 1652044,
      "date": "2022-07-15",
      "ratio": 20,
      "type": "forward",
      "accession": "0001652044-23-000016",
      "firstDisclosedAt": "2023-02-03"
    }
  ]
}

400 Bad Request

Invalid parameters

Response schema

error string
Human-readable error message

Example response

{}

403 Forbidden

Feature not available on current plan

Response schema

error string
Human-readable error message

Example response

{}