📜 UN Tender & Award Watch (UNGM Lifecycle)

Follow UN Global Marketplace tenders and awards through their lifecycle — new notices, and changes to deadline, type or status — as a change feed keyed on the source-native UNGM notice id. Public, logged-out UNGM search; no API key, login, cookie or CAPTCHA.

Output is one notice_record row per result; billing is pay-per-event, the value event being one notice delta (a $0.02 start fee per run, then $0.15 per notice delta plus one $0.10 source check per run that reads the source). Source: www.ungm.org.

Who it's for

Bid and capture teams tracking UN procurement, suppliers watching deadlines and awards, and procurement-intelligence teams that need a dated change feed rather than a one-off list.

📊 Sample Output

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

notice_id	deadline	published	notice_type	reference	country
314836	25-Sep-2026 23:59 (GMT 4.30)	17-Sep-2026	Invitation to bid	2026/FAAFG/FAAFG/138290	Afghanistan
314848	20-Sep-2026 16:00 (GMT 2.00)	17-Sep-2026	Request for quotation	rfx_11048_ROAS	Iraq
314832	04-Oct-2026 23:59 (GMT 1.00)	17-Sep-2026	Invitation to bid	2026/FNMOR/FNMOR/138248	Morocco
314828	01-Oct-2026 23:59 (GMT -5.00)	17-Sep-2026	Invitation to bid	2026/FLCOL/FLCOL/138333	Colombia
314844	28-Sep-2026 00:59 (GMT 2.00)	17-Sep-2026	Call for individual consultants	rfx_11042_ROAF	Morocco
314843	27-Sep-2026 13:00 (GMT 2.00)	17-Sep-2026	Call for individual consultants	rfx_10870_ROAF	Mauritania
314842	23-Sep-2026 13:00 (GMT 2.00)	17-Sep-2026	Call for individual consultants	rfx_10754_ROAF	Mauritania
314841	29-Sep-2026 13:00 (GMT 2.00)	17-Sep-2026	Call for individual consultants	rfx_11015_ROAF	Mauritania

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

✅ What you get

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. ungm:314836
• notice_id — e.g. 314836
• title — e.g. Procurement and Delivery of Hermetic Storage Bags
• deadline — e.g. 25-Sep-2026 23:59 (GMT 4.30)
• published — e.g. 17-Sep-2026
• agency — e.g. FAO
• notice_type — e.g. Invitation to bid
• reference — e.g. 2026/FAAFG/FAAFG/138290
• country — e.g. Afghanistan
• sustainable_flagged — e.g. False
• source_url — e.g. https://www.ungm.org/Public/Notice/314836
• record_type (string) — e.g. notice_record
• delta_type (string/null) — null in every sample row

What each record contains

A notice_record (snapshot) or notice-delta (watch) carrying the UNGM notice fields as listed, keyed on the source-native notice id. In watch mode each delta is NEW / CHANGED / REMOVED with before / after and changed_fields.

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)

{
  "title_contains": "",
  "page_size": 25,
  "pages": 1,
  "watch_mode": false,
  "max_items": 40
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.15 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. A smaller, narrowed run

{
  "title_contains": "",
  "page_size": 25,
  "pages": 1,
  "watch_mode": false,
  "max_items": 5
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
  "title_contains": "",
  "page_size": 25,
  "pages": 1,
  "watch_mode": true,
  "max_items": 40
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.15 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run aXsjr8TknFtLj15TS, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_key": "ungm:314836",
  "notice_id": "314836",
  "title": "Procurement and Delivery of Hermetic Storage Bags",
  "deadline": "25-Sep-2026 23:59 (GMT 4.30)",
  "published": "17-Sep-2026",
  "agency": "FAO",
  "notice_type": "Invitation to bid",
  "reference": "2026/FAAFG/FAAFG/138290",
  "country": "Afghanistan",
  "sustainable_flagged": false,
  "source_url": "https://www.ungm.org/Public/Notice/314836",
  "record_type": "notice_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 5
}

🔧 How it works

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

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

First run and later runs — read this first

This Actor sells change detection, not bulk export. There are two modes:

• Snapshot (watch_mode: false, the prefilled default): returns the current notices as a preview, hard-capped at 25 records regardless of max_items. Billed one source-check only — the preview records themselves are not billed. Use it to see the data right now.
• Watch (watch_mode: true): the first run seeds a private baseline and emits zero deltas (billed one source-check). Every run after emits one delta per change — this is where the value comes from. A run with no changes emits zero and bills only the source-check.

So a brand-new watch run returns nothing by design; point it at a schedule and the deltas start on the next change.

Source, scope and limits

UNGM public notice search (https://www.ungm.org/Public/Notice/Search), logged-out only. Snapshot mode is a capped preview, not a bulk record export. Terminal states: NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED. A zero with no evidence fails loud rather than exiting quietly.

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

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), 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).

💰 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.07
Notice Delta (notice-delta)	$0.15	$0.14	$0.12	$0.10

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

• 8 notice deltas: $0.02 start + $0.10 source check + 8 × $0.15 = $1.32
• 25 notice deltas: $0.02 start + $0.10 source check + 25 × $0.15 = $3.87
• 300 notice deltas: $0.02 start + $0.10 source check + 300 × $0.15 = $45.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); 5 further record(s) withheld. Use watch mode for the full change feed.. max_items is a hard ceiling on what is delivered and billed, never a target. 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.ungm.org. 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.ungm.org) 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: How many rows can one run return?
A: Up to max_items (default 300); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

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 watches actors?
A: Same output shape and billing model; this one covers www.ungm.org. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 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.
• Status says CAPPED → your cap (max_items) was reached → raise it for a bigger run.
• 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

• UK Contracts Finder New Tender Opportunity Watch — New UK public-sector tender opportunities as they are published
• UK Contracts Finder Tender Opportunity & Deadline Watch — UK Contracts Finder Tender Opportunity & Deadline Watch
• 🇬🇧 UK Find a Tender Watch — Tenders, Awards & Incumbents — Watch UK public procurement from the official Find a Tender OCDS feed: new tenders, award results and incumbent changes as deduplicated, delta-only e…
• World Bank Procurement Event Watch — World Bank procurement notices as they publish and change: new notices, contract awards, and status or submission-date changes, keyed on the source-n…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup 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.