# Japan IT Tender Changes: Eligibility & Deadlines (`a_a2ad/jp-it-tender-changes`) Actor

Review five Japanese IT procurement corrections: qualification criteria, RFI periods, identifiers and cancellations. Before/after facts with official sources. $0.01 per complete change; a dated snapshot, not live tender search.

- **URL**: https://apify.com/a_a2ad/jp-it-tender-changes.md
- **Developed by:** [Manabu Omae](https://apify.com/a_a2ad) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 verified tender changes

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Japanese IT Tender Changes

**Source-linked eligibility requirement changes, deadline amendments and cancellations for Japanese IT procurement.** Get before-and-after facts in structured JSON, with official documents, procurement stages, observation times and the context an Agent needs for further review.

Use the records to update a procurement watchlist, inspect a changed qualification requirement, distinguish a period extension from a submission deadline, or remove a cancelled tender from a workflow.

**Current snapshot: 5 curated correction records, checked on November 6, 2026 JST.** It includes one qualification change, two RFI information-period amendments, one public-solicitation reference correction and one cancellation. No record currently has a verified open submission window.

### What each result contains

- **The factual change:** previous value, revised value and the relevant locations in the source documents.
- **The procurement context:** issuer, procurement identifier, title and stage—competitive tender, public solicitation or request for information.
- **Typed dates and deadlines:** submission, participation and opening dates remain distinct; unknown dates remain unknown.
- **Evidence and remaining questions:** original and correction URLs, source observation times, source-specific reuse attribution and `needs_confirmation` notes.

Qualification facts support an eligibility review; they do not determine whether a particular supplier can participate. Combined requirements and other relevant conditions remain with the record.

### Current coverage

The known correction publication dates range from **October 29 to November 5, 2026**. The Hokkaido correction's publication date is unverified and is returned as `null`. All five records were observed on November 6 JST; the latest recorded source observation is **07:58:06 JST**.

| Procurement | Stage | Recorded correction | Deadline interpretation |
| --- | --- | --- | --- |
| [Hokkaido integrated forestry cloud system study](https://www.pref.hokkaido.lg.jp/fs/1/3/2/3/9/5/0/0/_/%E5%8C%97%E6%B5%B7%E9%81%93%E5%91%8A%E7%A4%BA%E7%AC%AC11576%E5%8F%B7%E6%AD%A3%E8%AA%A4%E8%A1%A8.pdf), Notice 11576 | Open competitive tender | Required certifications: **ISO27001 AND ISO9001 → ISO27001 AND ISO27017** | Participation application: November 11, 17:00 JST. Bidding/opening: November 16, 13:00 JST. An independent submission cutoff is not verified, so `status` is `unknown`. Other qualification conditions still apply. |
| [MHLW pension workflow/infrastructure functional improvements](https://www.mhlw.go.jp/stf/shinsei_boshu/choutatsujouhou/chotatu/j-wto-siryo/newpage_10534.html) | Request for information | Information-provision period: November 5 → December 17, 2026 | The original material-submission cutoff remains July 30, 17:00 JST. This amendment does not establish a reopened submission window. |
| [MHLW pension systems work for in-house data entry](https://www.mhlw.go.jp/stf/shinsei_boshu/choutatsujouhou/chotatu/j-wto-siryo/newpage_10535.html) | Request for information | Information-provision period: November 5, 2026 → January 14, 2027 | The original material-submission cutoff remains March 13, 17:00 JST. The recorded previous value reflects the earlier amendment. |
| [DIH numerical-analysis equipment maintenance](https://www.mod.go.jp/dih/8.11.2-262.pdf) | Public solicitation | Request number: **分-08-76 → 分-08-80** | Contract-interest application: November 20, 10:00 JST. This is a participation deadline, so submission-based `status` is `unknown`. |
| [MOD entrance/exit gate system data-migration support](https://www.mod.go.jp/j/budget/chotatsu/naikyoku/nyuusatu/2026/1029a.pdf), R8-S-0642 | Open competitive tender | Notice cancelled on October 29 | `status` is `cancelled`. The former bidding event is not presented as a current deadline. |

Under the status definition below, this snapshot contains **2 `closed`, 2 `unknown`, 1 `cancelled` and 0 `open` records**. The labels describe recorded submission deadlines or an explicit cancellation; they do not classify the entire procurement lifecycle.

### Query examples

Paste a JSON input into the Actor's Input tab, or pass the same object through an Apify API or Agent integration. All filters are optional and combine with AND.

#### Get the qualification amendment

```json
{
  "kind": "qualification",
  "procurement_stage": "open_competitive_tender",
  "limit": 10
}
```

This snapshot returns the Hokkaido correction. Both required certifications and the remaining participation conditions are retained in its context.

#### Review the two RFI period amendments

```json
{
  "kind": "deadline",
  "procurement_stage": "request_for_information",
  "limit": 10
}
```

#### Find the cancelled tender

```json
{
  "status": "cancelled"
}
```

#### Retrieve a specific procurement

```json
{
  "tender_id": "DIH-2026-246"
}
```

#### Get the complete current snapshot

```json
{
  "limit": 5
}
```

A query with `"status": "open"` currently returns no records. To retrieve the Hokkaido correction, omit publication-date filters because its correction publication date is unknown.

### Input reference

| Field | Accepted values and behavior |
| --- | --- |
| `kind` | `qualification`, `deadline`, `scope`, `cancellation`, `other`. Matches a change kind and returns the complete matching correction in this version. |
| `procurement_stage` | `open_competitive_tender`, `public_solicitation`, `request_for_information`. |
| `issuer` | Exact issuer ID or full displayed name. For example, `jp-hokkaido` or `JP-MHLW`. |
| `tender_id` | Exact procurement key from a result. Some keys are normalized identifiers: `MHLW-RFI-PAGE-*` refers to an official page ID, not an official tender number. |
| `status` | `open`, `closed`, `cancelled`, `unknown`, using the definition below. |
| `date` | Exact correction publication date, `YYYY-MM-DD`. |
| `date_from`, `date_to` | Inclusive correction publication-date range. Do not combine with `date`. Records with unknown correction dates are excluded when any date filter is used. |
| `as_of` | ISO8601 timestamp with seconds and an explicit offset. Omit it to use the actual current JST time. Future timestamps are rejected; a record observed after the requested instant is excluded. |
| `limit` | Integer from 1 to 100; default 20. Limits complete result records. |

Results with known correction dates are ordered newest first; corrections with unknown dates follow them.

Publication dates and observation times serve different purposes. `date` filters when a correction was published; `as_of` selects information already observed by that instant and evaluates its recorded submission deadline. It does not reconstruct an uncollected historical archive.

### Read the result correctly

The following is an **excerpt** from the Hokkaido record. Full results also contain the source URLs, document locations, typed deadlines, other qualification conditions and reuse attribution.

```json
{
  "tender_id": "2026-北海道告示第11576号",
  "procurement_stage": "open_competitive_tender",
  "changes": [
    {
      "kind": "qualification",
      "field": "required_certifications",
      "before": {
        "operator": "AND",
        "standards": ["ISO27001", "ISO9001"]
      },
      "after": {
        "operator": "AND",
        "standards": ["ISO27001", "ISO27017"]
      }
    }
  ],
  "correction": {
    "document_date": null
  },
  "status": "unknown",
  "status_scope": "recorded_submission_deadline_only",
  "needs_confirmation": true,
  "eligibility_guarantee": false
}
```

Holding one of the listed certifications does not establish eligibility. The Hokkaido record also flags the required registration, exclusion checks, relevant forestry/cloud-system experience and the conditional cooperative provision for review against the official documents.

#### Status and deadline precision

| Status | Meaning |
| --- | --- |
| `open` | A verified exact `submission` cutoff is later than `status_as_of`. |
| `closed` | That recorded cutoff has been reached or passed. |
| `cancelled` | An explicit cancellation is supported by the source. |
| `unknown` | A submission-based status cannot be established from the recorded evidence. |

Participation applications, questions, bidding/opening events and date-only periods are not substituted for submission cutoffs. Extending an RFI information/hearing period does not, by itself, extend the material-submission deadline. Consult `deadlines`, `confirmation_reasons` and the latest official notice before acting.

### Pricing

**$0.01 per returned complete correction record — $10 per 1,000 results. No Actor start fee. Platform usage for the run is included.**

| Query result | Result-event price |
| --- | ---: |
| 1 complete correction | $0.01 |
| 2 complete corrections | $0.02 |
| All 5 current corrections | $0.05 |
| No matching records | $0.00 |

All fields, evidence links and confirmation notes belonging to one returned correction are covered by that record's price. The same correction appears at most once within a run, and there is no additional custom charge for the same result. A later run that returns the same snapshot record is a separate, billable retrieval. Cache retrieved records with their `record_id` and `latest_source_observed_at` when reusing an unchanged snapshot.

Set `limit` to request a smaller set of complete records and use Apify's maximum charge setting to control the run budget. If the remaining event budget cannot cover the complete selected batch, the Actor stops before writing any result items instead of silently delivering a partial batch. A budget rejection produces no result-event charges.

Apify may charge separately for post-run storage access under your plan; see [Apify's pricing-model documentation](https://docs.apify.com/actors/running/actors-in-store).

### Sources, attribution and reuse

The records are independently extracted and normalized by **a\_a2ad** from notices published by the Ministry of Health, Labour and Welfare, Ministry of Defense, Defense Intelligence Headquarters and Hokkaido. Each record retains its official source URLs, processing attribution and source-specific reuse basis.

- **MHLW, MOD and DIH:** the selected notice facts were reviewed under the publishers' adoption of [Public Data License 1.0](https://www.digital.go.jp/resources/open_data/public_data_license_v1.0). Relevant pages are [MHLW terms](https://www.mhlw.go.jp/chosakuken/index.html), [MHLW exceptions](https://www.mhlw.go.jp/chosakuken/exhibit.html), [MOD terms](https://www.mod.go.jp/j/info/contents.html) and [DIH terms](https://www.mod.go.jp/dih/tos/).
- **Hokkaido:** the entry uses a limited public-facts assessment recorded as `public_facts_policy`, supported by the [Agency for Cultural Affairs' 2026 Copyright Text](https://www.bunka.go.jp/seisaku/chosakuken/seidokaisetsu/pdf/94383901_01.pdf), pages 5–6, and [Hokkaido's terms](https://www.pref.hokkaido.lg.jp/kz/dxs/opendata/hokkaido_od_kiyaku.html), sections 1(1) and 6(1). It does not claim a CC BY or Public Data License grant for this record.

Retain the source and processing attribution when reusing the data. Individual exceptions and third-party rights still apply. The product distributes factual records and official document links; source PDFs, forms, logos and standards texts are not bundled. The publishers do not endorse this Actor, and these records are not official government publications.

### Snapshot and limits

This version is a **curated observation snapshot**, with the dates shown above. A run queries the stored records; it does not recheck the source websites. Nationwide coverage, automatic refresh and notifications are not included. Later amendments or related procurement steps may exist.

Original and correction dates are stored separately from source observation times. Unknown values remain `null`; a source hash is included only where the exact document bytes were obtained. A record's `needs_confirmation` flag identifies further checks needed for its use, rather than silently filling missing facts.

Use the dataset for change review, watchlist maintenance and evidence-based Agent workflows. Participation, acceptance of a submission and supplier eligibility must be confirmed from the applicable official documents and current instructions.

# Actor input Schema

## `kind` (type: `string`):

Select a correction that includes this kind of change. All fields in the correction remain together.

## `issuer` (type: `string`):

Exact issuer ID or display name.

## `tender_id` (type: `string`):

Exact procurement ID from the dataset.

## `status` (type: `string`):

Open/closed use only a verified exact submission time. This is not a statement of eligibility or current ability to participate. Unknown times remain unknown.

## `date` (type: `string`):

Exact YYYY-MM-DD publication date. Do not combine with a date range. Records with an unknown correction date are excluded.

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

Inclusive lower YYYY-MM-DD publication date. Do not combine with exact date. Records with an unknown correction date are excluded.

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

Inclusive upper YYYY-MM-DD publication date. Do not combine with exact date. Records with an unknown correction date are excluded.

## `as_of` (type: `string`):

Optional ISO8601 instant with seconds and explicit offset. Defaults to actual current JST. Excludes sources observed later; future instants are rejected.

## `limit` (type: `integer`):

1 to 100 complete records. Each procurement and correction document is one logical result unit.

## `procurement_stage` (type: `string`):

Exact stage filter. Public solicitation and RFI are distinct from formal competitive tenders.

## Actor input object example

```json
{
  "limit": 20
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("a_a2ad/jp-it-tender-changes").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("a_a2ad/jp-it-tender-changes").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 '{}' |
apify call a_a2ad/jp-it-tender-changes --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,a_a2ad/jp-it-tender-changes"
        }
    }
}
```

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/cn2QrOixoGKH6wO5L/builds/V9x6MOGTGyndL60jM/openapi.json