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:

{
  "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. 조달청 나라장터 입찰공고정보서비스, 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

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

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