📣 SGX Financial Report & Disclosure Document Watch

Singapore Exchange financial-report and disclosure documents as they are lodged: annual, interim, quarterly, business-review, sustainability and summary reports plus information and disclosure statements, with the issuer, the document date and the SGX document link. SCOPE: this is the open financial-reports document feed. It is NOT the full SGX company-announcements stream, which SGX keeps behind an authorised API.

Output is one report_document_record row per result; billing is pay-per-event, the value event being one report document delta (a $0.02 start fee per run, then $0.05 per report document delta plus one $0.10 source check per run that reads the source). Source: api.sgx.com.

📊 Sample Output

Real rows from run LftMCIk9xZmeORCg8 on build 0.1.13 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

document_id	company_name	security_name	title	document_date	broadcast_date
539SSPNK3JNJFTTJ	BANK OF THE PHILIPPINE ISLANDS	MULTIPLE	Information Statement	2026-09-03	2026-09-07

The run finished with the status message: PARTIAL: emitted 1 item(s); DEPTH CAP: stopped at the 1-page hard cap (1 records) without reaching 10 consecutive pages free of 30-day arrivals. Documents broadcast inside the window but sitting deeper than this cap were

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_key (string/null) — e.g. sgx:539SSPNK3JNJFTTJ
• document_id — e.g. 539SSPNK3JNJFTTJ
• company_name — e.g. BANK OF THE PHILIPPINE ISLANDS
• security_name — e.g. MULTIPLE
• title — e.g. Information Statement
• document_date — e.g. 2026-09-03
• broadcast_date — e.g. 2026-09-07
• document_url — e.g. https://links.sgx.com/1.0.0/corporate-announcements/539SSPNK3JNJFTTJ/f7ad729ae18
• record_type (string) — e.g. report_document_record
• delta_type (string/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "page_size": 1,
  "pages": 1,
  "broadcast_window_days": 30,
  "report_types": [],
  "company_contains": [],
  "watch_mode": false,
  "baseline_id": "default"
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.05 report-document-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "page_size": 1,
  "pages": 1,
  "broadcast_window_days": 30,
  "report_types": [],
  "company_contains": [],
  "watch_mode": false,
  "baseline_id": "default"
}

A bounded run for checking the field shape before scheduling.

3. Watch mode on a schedule

{
  "page_size": 1,
  "pages": 1,
  "broadcast_window_days": 30,
  "report_types": [],
  "company_contains": [],
  "watch_mode": true,
  "baseline_id": "default"
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.05 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run LftMCIk9xZmeORCg8, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_key": "sgx:539SSPNK3JNJFTTJ",
  "document_id": "539SSPNK3JNJFTTJ",
  "company_name": "BANK OF THE PHILIPPINE ISLANDS",
  "security_name": "MULTIPLE",
  "title": "Information Statement",
  "document_date": "2026-09-03",
  "broadcast_date": "2026-09-07",
  "document_url": "https://links.sgx.com/1.0.0/corporate-announcements/539SSPNK3JNJFTTJ/f7ad729ae1823a9fbcd215ae0186e0bda1bbff20cd4c5112574d19bfefbb9341",
  "record_type": "report_document_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 0
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each report document delta is charged at the moment it is pushed (report-document-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

Source

SGX public financial-reports document feed (public, logged-out)

• https://api.sgx.com/financialreports/v1.0

Public, logged-out only — no API key, login, cookie or CAPTCHA.

Two dates, and which one means "new"

Every record carries both, and they are not the same thing:

field	what it is
document_date	the reporting period end the document covers — and the feed's sort key
broadcast_date	when SGX actually published it — the arrival clock

The gap between them is large and normal: measured across 6,000 records on 2026-07-27, the publication lag runs to a median of 105 days and a p90 of 114. SoftBank Group's annual report, for instance, carries document_date 2026-03-30 (its 31 March financial year end) and was broadcast on 2026-07-27 — SGX's own announcement page for it says Period Ended 31/03/2026 and Date & Time of Broadcast 27-Jul-2026 16:30:17.

Both dates are in the change signature. A watch that only signed document_date would call a four-month-old period date "stale" on the day the document was published.

How deep this Actor reads, and why it isn't a page count

SGX sorts this feed by document_date. Because publication lags the period date, a document broadcast today is not near the top of the feed — measured, a trailing-30-day arrival sits at median rank 103 and was found as deep as rank 2,362.

So depth is decided by broadcast coverage, not by a page number. This Actor keeps reading until 10 consecutive pages carry no document broadcast inside broadcast_window_days (default 30). Ten is measured, not guessed: the largest observed gap between two pages carrying a trailing-30-day arrival was 6 pages.

pages is a hard cap (default 40 = 4,000 records) that bounds the read if coverage is never reached. Hitting that cap is reported as a named PARTIAL — "DEPTH CAP" — never passed off as a complete read. Raise pages or narrow broadcast_window_days if you see it.

For reference, an earlier build of this Actor read a fixed 2 pages of 100. On the day it was measured that window saw 89 of the 94 documents broadcast in the trailing 30 days; the other five were not late, they were permanently invisible.

Snapshot mode is a PREVIEW

watch_mode: false returns at most 25 records, hard-capped in code regardless of any input, labeled output_mode: "preview". This actor sells change detection, not bulk record export.

Watch semantics

The first watch run stores a private baseline and emits zero deltas. Later runs emit NEW / CHANGED / REMOVED keyed on the source-native id with before / after and changed_fields. Billed deltas are capped at 500 per run; the overflow is reported as a named PARTIAL withholding, is never billed, and is re-detected on the next run.

Terminal states

NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED. A zero with no evidence FAILS loud rather than exiting 0 quietly.

This feed is seasonal. Budget for the season, not the average.

Arrivals are measured on the broadcast clock, and they are lumpy by construction: SGX issuers file annual reports in a cluster a few months after their financial year ends, and 31 March is the common one.

Measured 2026-07-27 across 6,000 records:

window	documents broadcast	rate
trailing 7 days	4	4.0 / week
trailing 30 days	94	21.9 / week
trailing 90 days	249	19.4 / week

The daily shape inside that 30-day window shows the season plainly — 9, 12 and 13 documents on 13, 14 and 15 July, then 4, then 1, then roughly one a day through to the end of the month.

So the 90-day rate is the one to budget against, not the 30-day peak and not a quiet week. At $0.05 a delta the value event carries roughly 89% of a weekly-run bill in season and about 62% out of it; on a daily schedule those become 54% and 19%. Either cadence is defensible here — unlike the low-frequency watches in this fleet, this feed genuinely moves most days in season, so a daily run buys real timeliness rather than paying for checks.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Source check (source-check)	$0.10	$0.09	$0.08	$0.07
Report Document Delta (report-document-delta)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price (watch mode, one delta per change):

• 1 report document deltas: $0.02 start + $0.10 source check + 1 × $0.05 = $0.17
• 25 report document deltas: $0.02 start + $0.10 source check + 25 × $0.05 = $1.37
• 100 report document deltas: $0.02 start + $0.10 source check + 100 × $0.05 = $5.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: PARTIAL: emitted 1 item(s); DEPTH CAP: stopped at the 1-page hard cap (1 records) without reaching 10 consecutive pages free of 30-day arrivals. Documents broadcast inside the window but sitting deepe. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by api.sgx.com. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (api.sgx.com) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other market announcement watches actors?
A: Same output shape and billing model; this one covers api.sgx.com. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• GOV.UK Press Release Feed — official search API — Press releases from the official GOV.UK search API — title, department, date, link. Filter by keyword or organisation. No API key; pay per release
• Korea DART Corporate Filing Watch — Snapshot or watch new corporate disclosure filings from Korea's DART system. Watch mode reports only newly appeared filings
• 📰 Press-Release Event Feed — Official Newsroom Watch — One deduped press-release event feed from buyer-supplied official newsroom feeds, with confirmed cross-feed deltas. No licensed wires
• Taiwan MOPS Material Information Watch — Taiwan listed-company material information (重大訊息) as published to the MOPS open data feed: subject, statute clause and event date, keyed on the sourc…
• TMX New Listings & Suspensions — Official TMX exchange events — new TSX/TSXV company listings and reviews/suspensions (delisting reviews, trading suspensions). Facts-only from the pu…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.