8-K EVENTS · /v1/companies/{ticker}/8k-events

The 8-K API, as JSON.

SEC Form 8-K filings, parsed into clean JSON with every SEC item code preserved — 1.01 agreements, 2.01 acquisitions, 5.02 executive departures, 7.01 Reg FD, and the rest. One ticker, one call, the material-event history you can build on.

Every response carries meta.source_filing_url, so any event you read traces straight back to the exact 8-K on sec.gov. Refreshed daily from EDGAR.

Free tier: 50 requests/day, no card. Part of the seven-endpoint Filingrail v1 API.

ITEM-CODE BREAKDOWN

Every 8-K is classified by item code.

An 8-K isn’t one kind of event — it’s a wrapper around dozens of them. The SEC tags each filing with item codes that tell you exactly what happened. Filingrail preserves those codes verbatim and pairs each with its human-readable title.

  • 1.01

    Entry into a Material Definitive Agreement

    The company signed a contract that matters — a credit facility, a major supply deal, a merger agreement, a licensing arrangement. The defining event for tracking deal flow.

  • 2.01

    Completion of Acquisition or Disposition of Assets

    An acquisition or divestiture closed. Pairs with Item 1.01 (the signing) to mark the start and end of a transaction.

  • 5.02

    Departure / Election of Directors or Officers

    A C-suite or board change — a CEO resigns, a CFO is appointed, a director departs. One of the most-watched item codes for governance and event-driven monitoring.

  • 7.01

    Regulation FD Disclosure

    Information the company chose to disclose publicly under Reg FD — often a press release, investor-deck reference, or pre-announcement. Frequently carries an exhibit under Item 9.01.

  • 9.01

    Financial Statements and Exhibits

    The attachments index. Lists the exhibits filed with the 8-K — press releases (EX-99.1), agreements, and supporting documents. Rarely appears alone; tags along with the substantive item.

Those five are the most-watched, but the endpoint returns every code the company filed, including:

  • 2.02 — Results of Operations and Financial Condition (earnings releases)
  • 3.01 — Notice of Delisting or Failure to Satisfy a Listing Rule
  • 4.01 — Changes in Registrant’s Certifying Accountant (auditor changes)
  • 5.07 — Submission of Matters to a Vote of Security Holders
  • 8.01 — Other Events (the catch-all)

SAMPLE RESPONSE

One filing. Its item codes. Its source URL.

A single 8-K can carry several item codes — here a 5.02 executive change with its 9.01 exhibit index. The shape is the same for every issuer: an array of events, each with its codes, wrapped in a meta block.

The source_filing_url field is the traceability contract. Click it and you land on the exact filing the record was parsed from — audit-grade by design.

GET /v1/companies/AAPL/8k-events · 200 OK
{
  "data": [
    {
      "accession_no": "0000320193-25-000071",
      "filed_at": "2025-11-01T16:31:00Z",
      "event_date": "2025-10-30",
      "items": [
        {
          "code": "5.02",
          "title": "Departure of Directors or Certain Officers; Election of Directors"
        },
        {
          "code": "9.01",
          "title": "Financial Statements and Exhibits"
        }
      ]
    }
  ],
  "meta": {
    "ticker": "AAPL",
    "cik": "0000320193",
    "as_of": "2026-06-04T07:00:11Z",
    "source_filing_url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000071/0000320193-25-000071-index.htm",
    "source_filing_date": "2025-11-01"
  }
}

Illustrative shape. Item-code titles match the SEC’s own filing labels.

HOW TO MONITOR 8-K EVENTS

Watch the events that move a position.

Monitoring 8-K events is four steps: subscribe, call the endpoint per ticker, filter on the item codes you care about, and trace each hit back to its filing. Here is the working pattern.

  1. 1

    Subscribe on RapidAPI

    Subscribe to the free Basic tier (50 requests/day, no card) and copy your X-RapidAPI-Key from the dashboard.

  2. 2

    Call the 8-K events endpoint

    Request the endpoint for each ticker you follow. Two headers, one path parameter.

  3. 3

    Filter by item code

    Keep the events whose codes intersect your watchlist — 5.02 for leadership changes, 1.01 + 2.01 for deals, 7.01 for Reg FD disclosures.

  4. 4

    Trace back to the source filing

    Open meta.source_filing_url on any record to confirm it against the original 8-K on sec.gov before you act on it.

curl
# 1. Pull the latest 8-K events for one issuer
curl --request GET \
  --url 'https://filingrail.p.rapidapi.com/v1/companies/AAPL/8k-events?limit=20' \
  --header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY' \
  --header 'X-RapidAPI-Host: filingrail.p.rapidapi.com'
Python · watchlist monitor
import os
import requests

HOST = "filingrail.p.rapidapi.com"
HEADERS = {
    "X-RapidAPI-Key": os.environ["RAPIDAPI_KEY"],
    "X-RapidAPI-Host": HOST,
}

# Watch a watchlist for new departure / acquisition events
WATCH_CODES = {"5.02", "2.01", "1.01"}

def new_material_events(ticker):
    resp = requests.get(
        f"https://{HOST}/v1/companies/{ticker}/8k-events",
        params={"limit": 20},
        headers=HEADERS,
        timeout=10,
    )
    resp.raise_for_status()
    for event in resp.json()["data"]:
        codes = {item["code"] for item in event["items"]}
        if codes & WATCH_CODES:
            yield {
                "ticker": ticker,
                "event_date": event["event_date"],
                "codes": sorted(codes & WATCH_CODES),
                # Every record traces back to the SEC filing it came from:
                "source": event,  # paired with meta.source_filing_url
            }

for hit in new_material_events("AAPL"):
    print(hit["event_date"], hit["codes"])

To catch filings the moment they reach EDGAR, pair this with /v1/filings/recent?type=8-K and resolve each hit through this endpoint.

HONEST SCOPE

What this endpoint is — and what it isn’t.

Clear boundaries save you an integration you’d have to rip out later.

What it is

  • Structured 8-K metadata per issuer: event date, accession number, and every SEC item code with its filing title.
  • A stable JSON envelope with meta.source_filing_url linking each record to the filing on sec.gov.
  • Daily-refreshed coverage drawn directly from SEC EDGAR — no scraping, no parser to maintain on your side.
  • Queryable by ticker or CIK, alongside six other v1 endpoints in the same API.

What it isn’t

  • Not the full free text of every exhibit — for the complete document, follow the source filing URL to sec.gov.
  • Not real-time intraday push. It is a daily-refreshed REST endpoint, not a websocket feed.
  • Not non-US filings — US SEC EDGAR filers only.
  • Not analysis or interpretation. It returns the item codes the company filed; the judgment is yours.

FAQ

8-K API questions.

Still wondering something? Email support@hudsonenterprisesllc.com — same business day response.

What is an 8-K filing?
A Form 8-K is the "current report" public companies file with the SEC to disclose material events between their regular quarterly and annual reports — things like acquisitions, executive departures, new agreements, and results announcements. Each 8-K is tagged with one or more SEC item codes (1.01, 2.01, 5.02, 7.01, 9.01, and others) that classify what kind of event it is.
What does the 8-K events endpoint return as JSON?
For a given ticker or CIK, it returns each 8-K filing with its event date, accession number, and the list of item codes attached — each code paired with its human-readable SEC title. Every response also carries a meta block with source_filing_url and source_filing_date so you can open the exact filing on sec.gov that the record came from.
How current is the 8-K data?
The corpus is refreshed daily from SEC EDGAR. New 8-K filings are ingested on the nightly run and typically appear in the API the following morning UTC. To catch filings the moment they hit EDGAR, pair this endpoint with the recent-filings stream and filter on form type 8-K.
Which 8-K item codes are supported?
All standard SEC 8-K item codes are preserved exactly as filed — including 1.01 (material agreement), 2.01 (completed acquisition/disposition), 2.02 (results of operations), 5.02 (officer/director changes), 7.01 (Reg FD), 8.01 (other events), and 9.01 (financial statements and exhibits). Filingrail does not collapse or re-bucket codes; you receive the same codes the company filed.
How do I monitor a specific event type, like executive departures?
Call the 8-K events endpoint for the tickers you follow and filter the returned items by code 5.02 (officer/director departures and elections). For deal tracking, filter on 1.01 (agreement signed) and 2.01 (acquisition completed). The "How to monitor 8-K events" section above shows a working Python pattern.
Is there a free tier?
Yes. The Basic tier on RapidAPI is $0 with 50 requests per day and no card required — enough to evaluate the 8-K events endpoint and the other six v1 endpoints. Pro is $9/mo for 5,000 requests/month, Ultra is $49/mo for 50,000, and Mega is $199/mo for 500,000.
Where does the data come from?
Directly from SEC EDGAR — no third-party data brokers. Every upstream request to EDGAR is sent with a compliant User-Agent header per the SEC’s fair-access policy, and every record in the response links back to the originating filing on sec.gov.
What is NOT in the 8-K events endpoint?
It returns the structured item-code metadata and filing reference for each 8-K — not the full free-text body of every exhibit. For the complete document, follow meta.source_filing_url to the filing on sec.gov. The endpoint also covers US SEC filers only; no non-US exchanges.

START FREE

Query 8-K events in a minute.

Subscribe to the free Basic tier on RapidAPI — 50 requests/day, no card — and the 8-K events endpoint, plus the other six v1 endpoints, are live with your key.

$0 Basic (50/day) · $9 Pro (5k/mo) · $49 Ultra (50k/mo) · $199 Mega (500k/mo).