New SEC Filings

Newly Published SEC Filings

Receive newly published SEC filings as they become available through the FinFeedAPI SEC Filings WebSocket API.

Establish a persistent WebSocket connection to receive a short backlog of recently discovered filings followed by a continuous stream of newly published SEC filings with an average broadcast latency of approximately 100 ms. Each event includes structured filing information such as the accession number, form type, filing date, acceptance time, company CIK, and filing description, allowing applications to react immediately to new regulatory disclosures.

Start with Free Credits Read the Documentation

What Are Newly Published SEC Filings?

Newly published SEC filings are regulatory documents that have just been accepted and published through the U.S. Securities and Exchange Commission's EDGAR system.

A live stream instead of polling

Instead of periodically polling the EDGAR archive for updates, applications can subscribe to a live stream that delivers filing notifications immediately after they are discovered. This enables systems to react to new regulatory disclosures without repeatedly querying historical datasets.

When a client connects to the WebSocket API, the server first delivers a short backlog of recently discovered filings to establish a consistent starting point. After the backlog has been transmitted, every newly published filing is streamed as it becomes available, allowing applications to maintain an up-to-date view of SEC activity through a single persistent connection.

Event-driven, not on-demand search

Unlike historical filing searches, which retrieve previously published filings on demand, the streaming interface continuously pushes new filing events to connected clients.

This event-driven model is well suited for applications that need immediate awareness of regulatory activity rather than periodic synchronization.

Why Stream Newly Published SEC Filings?

Many financial applications depend on immediate access to newly published regulatory filings. Receiving filings as they are published allows applications to respond to material corporate events, monitor regulatory disclosures, trigger downstream processing pipelines, and distribute updates without waiting for scheduled polling intervals.

Respond as soon as filings are discovered

Streaming newly published SEC filings helps applications:

monitor regulatory disclosures as they are published
trigger alerts when companies submit new filings
power financial news and event feeds
build live compliance monitoring systems
automate AI document ingestion workflows
synchronize filing databases as new submissions arrive
trigger filing extraction immediately after publication
reduce latency compared to periodic polling

Because filings are delivered continuously over a persistent connection, applications receive updates as soon as new filings are discovered rather than repeatedly querying the API for changes.

Live SEC Filing Stream

The FinFeedAPI WebSocket API provides a continuous stream of newly published SEC filings.

Backlog first, then live events

After establishing a WebSocket connection, the server immediately sends a backlog of recently discovered filings. These messages are identified by is_historical = true and help applications initialize their local state before live updates begin.

Once the backlog has been delivered, every new filing is pushed automatically with an average latency of approximately 100 milliseconds. Live filing events are marked with is_historical = false, allowing applications to distinguish between initialization data and newly published filings.

Because the connection remains open, applications receive filing events continuously without issuing additional requests, making the stream suitable for live monitoring and event-driven architectures.

Information included in each filing event

Each WebSocket message represents a single SEC filing discovered by the platform. A filing event contains the information required to identify the filing and begin downstream processing immediately.

Field	Description
accession_no	Unique SEC accession number
form	SEC filing form code (for example 10-K or 8-K)
description	Filing title published by the SEC
filing_date	Filing submission date
accepted_time	Time the SEC accepted the filing
discovered_time	Timestamp when the filing was first detected
cik	Central Index Key of the issuer
is_historical	Indicates whether the event belongs to the initial backlog or the live stream

The accession number included in every event can be used immediately with other SEC Filings API endpoints to retrieve filing metadata, extract filing sections, download original EDGAR documents, or convert XBRL filings into structured JSON.

Connection Lifecycle

The WebSocket stream is designed to provide a continuous view of newly published SEC filings while allowing applications to recover gracefully from reconnects and temporary interruptions.

A typical connection sequence

1Open a WebSocket connection
2Receive the recent filing backlog (is_historical = true)
3Receive live filing events (is_historical = false)
4Optionally receive heartbeat messages
5Reconnect when instructed

Applications always receive the backlog first, allowing them to initialize a consistent local state before switching to the live stream of newly published filings. The connection remains open until it is closed by the client or the server sends a reconnect instruction during maintenance.

From connect to live updates

Open WebSocket
Receive backlog
Live filing events
Optional heartbeats
Reconnect if instructed

Build Live SEC Filing Workflows

Newly published filings often become the entry point for automated regulatory data pipelines. Instead of waiting for scheduled synchronization jobs, applications can react immediately when a filing appears and continue processing it using the accession number included in the event.

A common workflow

1Receive a filing event
2Read the accession number
3Extract filing content, download original documents, or convert XBRL into JSON

This event-driven approach separates filing detection from document processing while allowing downstream systems to retrieve only the data required for each filing.

From event to analysis

Receive filing event
Accession number
Extract content
Download documents
Convert XBRL

Example WebSocket Filing Event

Each message delivered by the stream represents a single SEC filing discovered by the platform. The API uses the same WebSocket connection to deliver both backlog events and newly published filings. Applications can distinguish between them using the is_historical field.

Live filing event

json

{
  "type": "fillings",
  "is_historical": false,
  "discovered_time": "2024-02-25T12:34:56.123456Z",
  "form": "10-K",
  "description": "ACME CORP 10-K annual report.",
  "filling_date": "2024-02-24",
  "accepted_time": "2024-02-25T12:00:00Z",
  "accession_no": "0000123456-24-000001",
  "cik": 123456
}

Why Developers Stream Newly Published SEC Filings

Many regulatory workflows depend on learning about new filings as soon as they become available. A continuous WebSocket stream eliminates the need for repeated polling while allowing applications to react immediately to newly published disclosures.

Streaming helps developers

build live regulatory monitoring systems
trigger automated filing processing pipelines
detect corporate disclosure events as they occur
synchronize filing databases continuously
reduce polling overhead
power alerting and notification systems
provide live regulatory data to AI and analytics platforms
connect filing discovery with document extraction and XBRL conversion

For applications where timing matters, streaming newly published filings provides a direct path from SEC publication to downstream processing.

New SEC Filings

Start Streaming Newly Published SEC Filings

Receive newly published SEC filings through a persistent WebSocket connection with an average broadcast latency of approximately 100 milliseconds.

Initialize your application with a recent filing backlog, receive continuous live filing events, and use accession numbers to retrieve filing content, download original EDGAR documents, or convert XBRL filings into structured JSON through the FinFeedAPI SEC Filings API.