Use Synoptic alongside a press release ingestion system

Start from the actual monitored source

Decide whether you need an issuer newsroom, a commercial wire, a government release or a filing. Search the current Synoptic stream catalog and inspect the source description. Keep those categories separate: a government press release is not a commercial wire release, and an SEC filing is not necessarily a release.

Map the job to the interface

Build a clear provenance boundary

Label a source-linked stream post as a Synoptic-delivered post. Preserve the original publisher link and any source fields. If your application requires full release text, redistribution or AI processing, ask for an explicit answer for that source and use case before enabling those paths. We have not verified a blanket Synoptic license to resell full PR Newswire articles.

Use a narrow integration acceptance test

Select one accessible stream, follow it, save recent post IDs and observe live delivery. Reconnect deliberately and verify that a replay does not create duplicate alerts. The WebSocket lastPosts feature is capped at 50; use a separately planned history route for a longer outage.

What to bring to the conversation

Prepare required wires or issuer domains, languages, private/public company scope, fields, intended audience and required history. A source-specific answer is more useful than a generic request for “all press releases.”