# Japan Government Procurement Notice Watch (Procurement Portal) (`nexgenwatch/japan-p-portal-procurement-notice-watch`) Actor

Japanese central-government procurement notices from the government's own Procurement Portal (調達ポータル), read through its English WTO-covered search: case…

- **URL**: https://apify.com/nexgenwatch/japan-p-portal-procurement-notice-watch.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Business, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 procurement notice deltas

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Japan Government Procurement Notice Watch (Procurement Portal)

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.

### 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.

### Pricing

| Event | Price (FREE tier) |
|---|---|
| Actor start (`apify-actor-start`) | $0.02 one-time |
| Source check (`source-check`) | $0.10 |
| **Per delta (`procurement-notice-delta`)** | **$0.05** |

`source-check` ladder, GOLD-floored: **$0.10 / $0.09 / $0.08 / $0.067**.
Charged once per run after the source enumeration terminates — seed runs and
genuine-zero runs included. It is **not** charged when the source refused the
read: a run that never read the source has not performed a source check.

The per-delta value event (`procurement-notice-delta`) is the **primary** event and is priced at
**$0.05 per delta** at the FREE tier. Ladder, GOLD-floored:
**$0.05 / $0.045 / $0.04 / $0.0335** (FREE / BRONZE / SILVER / GOLD-PLATINUM-DIAMOND).
`source-check` still charges; it is no longer the headline event. Billed deltas
are capped at 500 per run and any overflow is reported as a withholding rather
than charged.

### 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.

# Actor input Schema

## `date_from` (type: `string`):

Inclusive lower bound on the notice's publishing start date. The portal rejects any other format.

## `date_to` (type: `string`):

Inclusive upper bound on the notice's publishing start date.

## `organisation_contains` (type: `string`):

Optional filter on the procuring ministry or agency.

## `pages` (type: `integer`):

Result pages to walk at 50 rows each (bounds runtime).

## `watch_mode` (type: `boolean`):

First run seeds a private baseline and emits ZERO deltas.

## `baseline_id` (type: `string`):

Names the private baseline so several watches can run side by side.

## Actor input object example

```json
{
  "date_from": "2026/07/01",
  "date_to": "2026/07/25",
  "organisation_contains": "",
  "pages": 1,
  "watch_mode": true,
  "baseline_id": "default"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "date_from": "2026/07/01",
    "date_to": "2026/07/25",
    "organisation_contains": "",
    "pages": 1,
    "watch_mode": false,
    "baseline_id": "default"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/japan-p-portal-procurement-notice-watch").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "date_from": "2026/07/01",
    "date_to": "2026/07/25",
    "organisation_contains": "",
    "pages": 1,
    "watch_mode": False,
    "baseline_id": "default",
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/japan-p-portal-procurement-notice-watch").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "date_from": "2026/07/01",
  "date_to": "2026/07/25",
  "organisation_contains": "",
  "pages": 1,
  "watch_mode": false,
  "baseline_id": "default"
}' |
apify call nexgenwatch/japan-p-portal-procurement-notice-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/japan-p-portal-procurement-notice-watch"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vF4HK0HCgo2YuLrNN/builds/tzwp5WiX5mTv4nnfa/openapi.json