# Korea Tender Notice Changes (공고 변경이력) — What Moved and When (`atomo-studio/korea-g2b-notice-changes`) Actor

Amendments to Korean government tender notices: which field changed, its value before and after, and when. Catches moved opening dates and deadlines. From the Public Procurement Service (조달청). No Korean API key needed.

- **URL**: https://apify.com/atomo-studio/korea-g2b-notice-changes.md
- **Developed by:** [Atomo Studio](https://apify.com/atomo-studio) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 75.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 notice amendments

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?

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

## Korea Tender Notice Changes (공고 변경이력) — What Moved, and When

A Korean public tender is not fixed once it is posted. Opening dates get pulled
forward, submission deadlines slide, budgets are revised, eligibility is narrowed.
The notice is quietly amended and the original text is replaced.

If you are preparing a bid, that is the failure mode that actually costs you the
contract — not losing on price, but showing up to an opening that already happened.

**This Actor returns the amendments themselves**: which field changed, what it was
before, what it is now, and when the change was made. Roughly **9 out of 10 are
schedule changes**.

### What you get

One record per amended field:

```json
{
  "notice_no": "R26BK01672018",
  "category": "Goods",
  "changed_field_ko": "개찰일시",
  "changed_field_en": "Opening date/time",
  "value_before": "2026-09-04T10:00:00",
  "value_after": "2026-08-31T09:45:00",
  "is_schedule_change": true,
  "changed_at": "2026-08-24T08:47:06",
  "change_area_ko": "개찰결과",
  "url": "https://www.g2b.go.kr/link/PNPE027_01/single/?bidPbancNo=R26BK01672018&bidPbancOrd=000",
  "source": "조달청 나라장터 (Public Procurement Service, Korea) via data.go.kr"
}
```

That record says: the opening was moved **four days earlier**. Anyone working to the
original date would have missed it.

| Group | Fields |
|---|---|
| **The change** | `changed_field_ko`, `changed_field_en`, `value_before`, `value_after`, `changed_at`, `change_area_ko`, `is_schedule_change` |
| **Identity** | `notice_no`, `notice_seq`, `bid_class_no`, `rebid_no`, `category`, `url` |

`changed_field_en` is filled in for the fields that move most often (opening time,
submission deadline, budget, eligible region, licence restriction…). Anything outside
that vocabulary keeps the Korean original rather than getting a guessed translation.

Date-like values are converted to ISO 8601 on both sides, which matters here: the
upstream API often returns the *before* and *after* values in **different formats**
(`2026/09/04 12:00` vs `202608240900`), so a naive diff is unreadable.

### Input

Every field is optional. The default is the last 7 days across all three categories.

| Field | Type | Notes |
|---|---|---|
| `startDate` / `endDate` | date | `YYYY-MM-DD`, Korea time |
| `categories` | array | `goods`, `construction`, `service` |
| `keywords` | array | Match on the changed field name or its values |
| `scheduleChangesOnly` | boolean | Keep only amendments that moved a date or deadline |
| `maxItems` | integer | Stop after N records. `0` = no limit |

Foreign procurement (외자) has no change history upstream, so it is not offered.

**Amendments are rare — roughly 10 a day across all categories.** That is the point:
low volume, high consequence. Widen the date window if you want a fuller picture; a
7-day run returns about 70 records in under a second.

### Who this is for

- **Bidders** monitoring tenders they are actively preparing — the alert you cannot
  get from the notice itself, because the notice simply shows the new value
- **Bid-support and monitoring tools** that need a change feed rather than a snapshot
- **Analysts** studying how often, and how far, agencies move their own deadlines
- **AI agents** watching a shortlist of tenders for material change

Pairs with **Korea Public Tenders (나라장터)** — that Actor gives you the notices as
they stand, this one tells you what has moved since. Join on `notice_no`.

### Notes

**Source.** [조달청 나라장터 입찰공고정보서비스](https://www.data.go.kr/data/15129394/openapi.do),
published on Korea's national open-data portal under an unrestricted licence
(이용허락범위 제한 없음). Every record carries a `source` field and a `url` back to
the original notice.

**This is an API client, not a scraper.** Data comes from the government's own REST
API with a registered key. The g2b.go.kr website is never touched, so nothing here
breaks when the site is redesigned.

**No personal data.** Contact details are stripped from every text field and are
never emitted.

***

### Development

```bash
export G2B_SERVICE_KEY='...'   # data.go.kr 인증키 (다른 g2b Actor와 같은 키)
python3 probe.py               # 오퍼레이션·필드명 대조
apify push                     # 배포
```

업스트림 필드가 바뀌면 조용히 빈 값이 나간다. 이상하면 `probe.py`부터 돌릴 것.

# Actor input Schema

## `startDate` (type: `string`):

Earliest change date, YYYY-MM-DD (Korea time). Defaults to 7 days ago. Amendments are rare - widen the window for more.

## `endDate` (type: `string`):

Latest change date, YYYY-MM-DD (Korea time). Defaults to today.

## `categories` (type: `array`):

Which kinds of tender to include. Foreign procurement has no change history upstream.

## `keywords` (type: `array`):

Keep only changes matching one of these - a field name or a value. Korean or English, e.g. 개찰일시, 마감.

## `maxItems` (type: `integer`):

Stop after this many changes. Amendments are rare - roughly 10 a day across all categories. 0 = no limit.

## `scheduleChangesOnly` (type: `boolean`):

Return just the amendments that moved a date or deadline - the ones that break a bid you are already preparing.

## Actor input object example

```json
{
  "categories": [
    "goods",
    "construction",
    "service"
  ],
  "keywords": [],
  "maxItems": 0,
  "scheduleChangesOnly": false
}
```

# Actor output Schema

## `changes` (type: `string`):

One record per amended field - what changed, before and after.

## `downloadCsv` (type: `string`):

The same records as a spreadsheet.

# 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("atomo-studio/korea-g2b-notice-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("atomo-studio/korea-g2b-notice-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 atomo-studio/korea-g2b-notice-changes --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,atomo-studio/korea-g2b-notice-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/gJ7FTbaJbVeTVcA9J/builds/buohFQQ77b2Mm3n83/openapi.json