BLS News Releases

planned Executive · Tier 2 · RSS feed · Department of Labor (Bureau of Labor Statistics)

Official site (opens in a new tab) · All sources

What this source is

The Bureau of Labor Statistics publishes the government's most market-sensitive statistical releases — the Employment Situation, CPI, and workplace-injury reports — with documented news-release RSS feeds and a developer API. Statistical releases do not flow through the DOL newsroom feed we already ingest.

Identity and registry record

Registry id

bls-news

Agency / parent organization

Department of Labor (Bureau of Labor Statistics)

Branch

executive

Type

RSS feed

Status

planned

Tier

2

URL (home)

https://www.bls.gov/newsroom/ (opens in a new tab)

URL (index)

https://www.bls.gov/feed/ (opens in a new tab)

Registered

2026-07-28

Registry notes

Feeds page documented at bls.gov/feed (2026-07-28). Probe 2026-07-28: the guessed URL bls.gov/feed/news_release.rss returned 404 — the convention guess was wrong; robots and host are open (robots.txt HTTP 200, no block). Next step: fetch the bls.gov/feed documentation page itself through AgencyClient to read the exact feed URLs, then re-probe. Resolved 2026-07-31 (operator machine, off the server budget) by doing exactly that: bls.gov/feed/ answers HTTP 200 to our identified client and documents about 55 feeds, and NONE of them is an agency-wide news-release stream. The list is two families: ~42 per-program release feeds (empsit.rss, cpi.rss, ppi.rss, jolts.rss, ...) and ~13 *_latest.rss 'Latest Numbers' data feeds. Sampled evidence: empsit.rss is Atom, 12 items, every one with a guid and a date, ~259-character descriptions, linking to the real news-release pages — genuinely ingestible; bls_latest.rss is a single-item dashboard rollup with no guid, not a news stream. bls.gov/newsroom/ advertises no feed and autodiscovers none. So the correct registered address is the feed directory, not a feed: one registry entry cannot represent this source honestly. Left planned. The right shape is a fan-out — one entry per program feed, starting with the market-sensitive ones (empsit, cpi, ppi, jolts, eci, realer) — or a multi-feed adapter; either is a new-source decision, not a URL correction. Note for whoever picks it up: bls.gov returns 403 to unidentified fetchers but 200 to ours, so read its documentation through AgencyClient. Re-probe through scripts/check_sources.py, 2026-07-31: verdict html-only against the feed directory — HTTP 200, 66 KB, 7,591 characters — which is the accurate verdict, because the registered address is a catalogue of feeds and not a feed. Probed 2026-07-31: registered URL returned 404 (https://www.bls.gov/feed/news_release.rss) — the publisher moved or retired it; not a refusal.

How we ingest it

Channel

RSS feed

Method

Would poll the documented news-release feeds daily; the v2 API (api.bls.gov, registered key, 500 queries/day) is a later data extension.

Request budget

the agency class: at most 1,500 requests per day shared across every agency web source, counted from the fetch log (failed requests count too)

Politeness

robots.txt is honored as observed — including each host's crawl-delay, exactly — and every request identifies itself as fapd/0.1 (Free Agentic Publication Digester; +https://fapd.info/bot.html; contact: hustleyourcity@gmail.com); a refusal is recorded, never evaded

Capture and hash

captured raw content is hashed (SHA-256) into the day's committed provenance manifest, hash-chained day to day (PROVENANCE.md)

Ingestion health

Not ingested: the registry status of this source is planned.

Ingestion statistics

These figures describe this project's ingestion of this source — items we recorded and requests we made — and nothing else. They are not a measurement of the publisher.

Not ingested: the registry status of this source is planned. Ingestion statistics are measured for active sources only.

All time

Last 30 days, day by day

No requests and no items were recorded in the last 30 days, so there is nothing to chart.