Use Synoptic for SEC filing events alongside official SEC data

Use the right stream ID

The current canonical stream is SEC Edgar Filings | GOV Releases, ID 01JSPH2HZMMND30770DECW091Q. Anonymous MCP get_stream returned an ACTIVE stream with apiAccessEnabled: true on 2026-11-14. Its description labels it NO DELAY.

The delayed catalog entry is a different stream. Search results include multiple SEC tiers, including variants without API access. Pin the verified ID after checking metadata; a similar name is not evidence of the same entitlement or delay policy.

Connect the event to official evidence

The event payload’s precise SEC fields were not tested with a subscriber account. Do not assume every post contains an accession, a complete 10-K, a parsed statement or every exhibit. Inspect a permitted sample before writing your mapping.

• Confirm account entitlement and API access to the chosen SEC stream.
• Receive stream.post.created through a reader-key WebSocket connection filtered to the stream ID.
• Persist the raw event, post ID, stream ID and receipt time before enrichment.
• Use sourceLink when present; validate any accession or document reference against official SEC records.
• Use the official submissions or XBRL API for the corresponding metadata or financial observations.
• Save the resulting citation and record parsing failures separately from missing events.

Recover with an explicit time window

The WebSocket guide supports lastPosts for at most 50 recent posts across the connected streams. For longer gaps, query accessible history with the REST API and retain the pagination cursor and date bounds. Then reconcile the relevant interval against official filing metadata or indexes.

The REST reference describes one-request-per-second retrieval limits. Use history for recovery and targeted queries; use a live subscription for incoming events. Never describe the bounded reconnect window as guaranteed replay of every missed filing.

What remains account-dependent

Public discovery and stream inspection were successfully exercised. Authenticated post reads, WebSocket delivery, complete coverage, retention and end-to-end latency were not tested. The description’s package-only wording and packageOnly: false metadata disagree, so confirm current access in the product.

The right next step is an access check with the actual stream and desired use. The official API quickstart remains available when you simply need filing metadata without a commercial account.