📜 Japan Government Procurement Notices Scraper

Scrape Japanese government procurement notices from the national portal: agency, title, deadline and category. Run it once and you get the current records as a dataset — that is the default. Turn on watch mode and a scheduled run returns only what changed since the last run (see Optional: run it on a schedule).

Japanese central-government procurement notices from the government's own Procurement Portal (調達ポータル), read through its English WTO-covered search: case number, English case name, procuring ministry, prefecture and the notice events attached to the case. Keyed on the portal's 19-digit case number.

Output is one procurement_notice_record row per result; billing is pay-per-event, the value event being one procurement notice delta (a $0.02 start fee per run, then $0.05 per procurement notice delta plus one $0.10 source check per run that reads the source). Source: www.p-portal.go.jp.

Who buys this

Buyers usually search for Japan government procurement or Japan tenders.

• Bid teams and suppliers following Japan government procurement in their category.
• Procurement-intelligence vendors and consultancies tracking Japan tenders and incumbents.
• Analysts researching who buys what from whom in the public sector.

📊 Sample Output

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

case_number	case_name	organisation	location	notice_events
0000000000000582555	Helpdesk operations for the Government Solution Services	Digital Agency	Tokyo	Public notice 2026/03/27 Public end | Public notice 2026/07/23 Public
0000000000000596249	Hardware, design, development and maintenance of Trading and Portfolio	Ministry of Finance	Tokyo	Public notice 2026/05/12 Public end | Public notice 2026/07/08 Public
0000000000000596256	Data center, network and operation service for Trading and Portfolio M	Ministry of Finance	Tokyo	Public notice 2026/05/18 Public end | Public notice 2026/07/15 Public
0000000000000601150	Phase I development of a new House Legislation Information Network Sys	House of Representatives	Tokyo	Public notice 2026/06/12 Public end | Public notice 2026/07/17 Public
0000000000000601871	Environment setup and system usage related to the search system for la	Supreme Court	Tokyo	Public notice 2026/06/22 Public end | Public notice 2026/07/13 Public
0000000000000601919	Environment setup and system usage related to the search system for le	Supreme Court	Tokyo	Public notice 2026/06/22 Public end | Public notice 2026/07/13 Public
0000000000000605535	Lease,maintenance,installation and adjustment work for Inmarsat EGC co	Ministry of Land, Infrastructure and Transport	Tokyo	Public notice 2026/07/01 Public start Bid
0000000000000607937	Lease for radio monitoring vehicle In FY 2026	Ministry of Internal Affairs and Communications	Tokyo	Public notice 2026/07/06 Public start Bid

The run finished with the status message: PARTIAL: emitted 25 item(s); PREVIEW: snapshot output is capped at 25 record(s); 25 further record(s) withheld. Use watch mode for the full change feed.

✅ What you get

One row per record delivered by Japan Government Procurement Notice Watch (Procurement Portal); in watch mode a delta row carries delta_type, before, after and changed_fields. Field names come from the actor's real output; fields the source does not publish are null.

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. jpp:0000000000000582555
• case_number (string/number/integer/boolean/null) — e.g. 0000000000000582555
• case_name (string/number/integer/boolean/null) — e.g. Helpdesk operations for the Government Solution Services
• organisation (string/number/integer/boolean/null) — e.g. Digital Agency
• location (string/number/integer/boolean/null) — e.g. Tokyo
• notice_events (string/number/integer/boolean/null) — e.g. Public notice 2026/03/27 Public end | Public notice 2026/07/23 Public start Bid
• record_type (string) — e.g. procurement_notice_record
• delta_type (string/null) — null in every sample row
• before (object/array/string/number/integer/boolean/null) — null in every sample row
• after (object/array/string/number/integer/boolean/null) — null in every sample row
• changed_fields (array/object/string/null) — null in every sample row
• observed_at (string/null) — null in every sample row

✅ What you get

✅ What you get

• record_key (string/null) — e.g. jpp:0000000000000581089
• case_number (string/number/integer/boolean/null) — e.g. 0000000000000581089
• case_name (string/number/integer/boolean/null) — e.g. Construction and maintenance of Network for migration to the Government Solution
• organisation (string/number/integer/boolean/null) — e.g. Digital Agency
• location (string/number/integer/boolean/null) — e.g. Tokyo
• notice_events (string/number/integer/boolean/null) — e.g. Public notice 2026/03/25 Public end | Public notice 2026/07/10 Public start Bid
• record_type (string) — e.g. procurement_notice_record
• delta_type (string/null) — null in every sample row
• before (object/array/string/number/integer/boolean/null) — null in every sample row
• after (object/array/string/number/integer/boolean/null) — null in every sample row
• changed_fields (array/object/string/null) — null in every sample row
• observed_at (string/null) — null in every sample row

✅ What you get

• record_key (string/null) — e.g. jpp:0000000000000581089
• case_number — e.g. 0000000000000581089
• case_name — e.g. Construction and maintenance of Network for migration to the Government Solution
• organisation — e.g. Digital Agency
• location — e.g. Tokyo
• notice_events — e.g. Public notice 2026/03/25 Public end | Public notice 2026/07/10 Public start Bid
• record_type (string) — e.g. procurement_notice_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)

{
  "date_from": "2026/07/01",
  "date_to": "2026/07/25",
  "pages": 1,
  "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 procurement-notice-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. Optional watch mode (changes only, for a schedule)

{
  "date_from": "2026/07/01",
  "date_to": "2026/07/25",
  "pages": 1,
  "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 32f8Wwp8lCDUHjRIA, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_key": "jpp:0000000000000582555",
  "case_number": "0000000000000582555",
  "case_name": "Helpdesk operations for the Government Solution Services",
  "organisation": "Digital Agency",
  "location": "Tokyo",
  "notice_events": "Public notice 2026/03/27 Public end | Public notice 2026/07/23 Public start Bid",
  "record_type": "procurement_notice_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 25
}

🔧 How it works

Source. The actor reads www.p-portal.go.jp — endpoints: https://www.p-portal.go.jp. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Watch semantics. Snapshot mode (watch_mode: false) returns a preview capped at 25 records. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each procurement notice delta is charged at the moment it is pushed (procurement-notice-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.

🔧 How it works

🔧 How it works

🔧 How it works

Source

Japan Procurement Portal English procurement search (public, logged-out)

• https://www.p-portal.go.jp/pps-web-biz/UAA01/OAA0100?OAA0116

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

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.

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

⏰ Optional: run it on a schedule

A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true) so each run returns only the changes, 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).

⏰ Optional: run it on a schedule

A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console → Schedules → Create new, add this actor with the watch-mode input above (watch_mode: true) so each run returns only the changes, and pick a cadence:

💰 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.067
Procurement Notice Delta (procurement-notice-delta)	$0.05	$0.045	$0.04	$0.0335

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

• 8 procurement notice deltas: $0.02 start + $0.10 source check + 8 × $0.05 = $0.52
• 25 procurement notice deltas: $0.02 start + $0.10 source check + 25 × $0.05 = $1.37
• 100 procurement notice 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 25 item(s); PREVIEW: snapshot output is capped at 25 record(s); 25 further record(s) withheld. Use watch mode for the full change feed.. 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 www.p-portal.go.jp. It collects only what the source publishes to any visitor, 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 (www.p-portal.go.jp) 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 public procurement scrapers actors?
A: Same output shape and billing model; this one covers www.p-portal.go.jp. 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; 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

• CanadaBuys Tenders and Awards Scraper — Scrape Canadian federal tenders and contract awards from CanadaBuys: title, buyer, closing date, supplier and value. Every run returns the current re…
• EU TED Tenders and Contract Awards Scraper — Scrape EU Tenders Electronic Daily notices: tenders and contract awards with buyer, supplier, value and CPV codes. Every run returns the current reco…
• Singapore GeBIZ Tenders and Awards Scraper — Scrape Singapore government tenders and awards from GeBIZ: agency, title, closing date, supplier and value. Every run returns the current records as…
• UK Contracts Finder Contract Awards Scraper — Scrape UK Contracts Finder contract awards: buyer, supplier, value, dates and repeat-award incumbents. Every run returns the current records as a dat…
• UK Contracts Finder Awards Scraper — Scrape UK Contracts Finder contract award notices: buyer, supplier, value and award date. Every run returns the current records as a dataset. Optiona…
• UK Contracts Finder Tender Deadlines Scraper — Scrape UK Contracts Finder tender deadlines: notice, buyer, closing date and deadline changes. Every run returns the current records as a dataset. Op…
• 🏢 About NexGen Watch — NexGen Watch is a catalog of more than 300 public data 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.