Worked acceptance sheet
| Routine private-company release | Wire RSS / publisher feed / source stream | Release metadata with issuer and stable identity | Not established by a listed-company symbol query. |
| Major listed-company development | Finnhub /press-releases?symbol=... | majorDevelopment item and source-specific access | Documented schema; synthetic mapping only. |
| Named-wire metadata query | newsfilter source.id:prNewswire | Returned source ID, record ID and source link | Documented query; authenticated response not called. |
| PR Newswire / GlobeNewswire stream monitoring | Synoptic named Tier 3 streams | API-enabled stream metadata, then permitted reader response | Catalog metadata observed; post response requires access. |
| Correction replay behavior | Local RSS-file workflow | new -> replay -> correction -> old replay | Eight offline tests include durable-state CLI behavior. |
No matching records in this selected table. Try a name or identifier, or consult the original source.
Next task for a developer
Run the complete RSS conversion, inspect its expected JSON and exercise correction handling. These tasks produce working local artifacts before any vendor credential is available.
What a real feed trial still needs
Use your required issuer types, languages and wires. Record account restrictions separately from missing items. Audit financial tables and attachments only when entitled to their content. No result in this guide claims complete wire recall or measured arrival speed.
Source notes
- Finnhub press releases ↗
Selected major developments and Enterprise full-text boundary.
- newsfilter source-filter query ↗
Exact request shape and article metadata.
- Synoptic public stream catalog ↗
Anonymous streams_all observed on 2026-11-14 across all three pages. Metadata and source descriptions, not licensed article bodies or measured latency.
Next step
Evaluate a Synoptic release workflow
Start with the sources and fields the monitoring task requires.
Evaluate a Synoptic release workflow