# World Bank Procurement Notice Change Monitor (`maydit/world-bank-procurement-notice-monitor`) Actor

Track World Bank-financed procurement notices, buyer organizations, project IDs and deadline changes. Export source-labeled bid, expression-of-interest and award notices without an API key.

- **URL**: https://apify.com/maydit/world-bank-procurement-notice-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 saved observations

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/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

![World Bank Procurement Notice Change Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/world-bank-procurement-notice-monitor-b20d0b3fa31c.png)

## World Bank Procurement Notice Change Monitor

Turn public World Bank-financed procurement notices into a reviewable bid watchlist. Export stable OP notice IDs, project identity, buyer organizations and source deadlines, then see exactly which source fields changed on later complete checks.

**Best for:** engineering firms, IT vendors, infrastructure suppliers and consulting teams screening international procurement notices. No API key or login is required.

### Start with three notices

Run with the default input, or paste:

```json
{"maxResults":3}
```

Open **Dataset** for source observations, **SUMMARY** for coverage and missing IDs, or **RUN_REPORT** for a readable report. Export JSON/CSV, or call the Actor from an existing API/MCP workflow. Scheduling and external delivery are configured by you in Apify; the Actor does not create schedules or send messages.

### What makes this useful

- One saved row per real source notice, with both OP notice ID and parent project ID.
- Source dates, raw closing time and notice status remain visible. `Published` is not converted into an unsupported “open bid” claim.
- Exact-ID watchlists surface changed deadlines, statuses, descriptions and buyer fields; previous observations and changed field names are retained.
- Failed requests, incomplete output and missing IDs stay in coverage diagnostics. They do not become billable synthetic leads.

### Three ready-to-use workflows

#### Review three procurement notices

Inspect a three-notice source window and distinguish notice type, published status and reported deadlines.

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

#### Track two infrastructure notices

Compare two exact World Bank notices for source deadline, status and description changes.

```json
{
  "noticeIds": [
    "OP00481623",
    "OP00481628"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "infrastructure-notices"
}
```

#### Find water procurement notices

Use World Bank full-text search for water and review three source notices with buyer and project identity.

```json
{
  "keyword": "water",
  "maxResults": 3,
  "comparePrevious": false
}
```

The exact watchlist examples are reproducible historical/public records, not a promise that those opportunities are currently open. Replace the IDs with notices you qualify. Keyword matching uses the source's full notice text, so a result title need not contain the keyword. Optional `projectId` restricts discovery to one exact project. When `noticeIds` is supplied, it overrides both search filters.

### Read the dates correctly

`noticeType` distinguishes invitations, expressions of interest, prequalification, general procurement notices and award notices. `noticeStatus` is the source status. Neither alone establishes eligibility, an active solicitation or a contract award to your business.

`deadlineDateRaw` and `deadlineTimeRaw` preserve source fields. `deadlineDate` extracts the calendar date only when the source format is recognized. `deadlineDateStatus` compares that date with `deadlineAsOfUtcDate`: before, on or after the observation UTC date. **This is not a local closing-time calculation.** `deadlineTimezone` is null and `bidOpenStatus` is always `not_determined`. Even if the API date contains a Z suffix, we do not combine it with a separately reported local clock time and invent a timezone. Older/conflicting dates can appear in the original notice body; always follow `sourceUrl` and confirm the closing date with the procuring organization.

### Main output fields

| Field | Meaning |
| --- | --- |
| noticeId, projectId | Source OP notice and P project identities |
| title, noticeType, noticeStatus | Source description, notice class and reported status |
| countryName, buyerOrganization | Published country label and institutional buyer; optional in source |
| bidReference, procurementMethodCode | Source procurement reference/method when supplied |
| noticeDateRaw, noticeDate | Raw publication label and recognized calendar date |
| deadlineDateRaw, deadlineTimeRaw | Original source deadline values, not normalized to a guessed timezone |
| deadlineChanged, statusChanged | Comparison flags; null before a prior comparable observation exists |
| comparisonStatus, changedFields, previous | Exact saved-observation comparison evidence |
| sourceUrl, observedAt | Official notice link and retrieval time |

No tender-value estimate, winner, email/phone enrichment, personal contact list or sales-intent score is produced. Public buyer organizations are not verified prospective customers.

### Monitoring and coverage

Discovery reads the **first source window**, sized by `maxResults` (1–100), with no bulk pagination. Exact-ID mode reads up to 10 IDs, one request each, at least one second apart. The source controls search ordering; a bounded window is not a census or assurance of the newest notice.

Enable `comparePrevious` for sequential runs with the same IDs or query, window and `snapshotName`. First observation is `new`; later fields are `changed` or `unchanged`. `onlyChanges` also enables comparison and can correctly save zero rows on an unchanged repeat. Changes are observed source differences, not necessarily new publication events.

History is stored in the named `world-bank-procurement-notice-monitor-history` key-value store. A complete run may update records it actually observed. Absent or no-longer-selected notices are **not** declared withdrawn or removed. Query windows retain prior positive observations. Source failures, charge caps, interrupted output or time limits prevent the entire run's baseline from advancing. Run the same snapshot sequentially to avoid concurrent writers.

`SUMMARY.selectedWindowComplete` describes the requested selection; `sourceUniverseComplete` describes whether the source reported more matches. A completed first window can have `incomplete:false` and `sourceUniverseComplete:false`. Exact missing IDs appear in `notFoundNoticeIds`; an empty exact lookup is not evidence of withdrawal. If every source request fails, the run fails clearly. HTTP 401/403/429 or other non-200 responses are not bypassed or repeatedly retried.

### Pricing and limits

Standard result price: **$0.002 per saved notice**, plus **$0.00005 Actor Start**. Three records total $0.00605 in Actor event charges; 100 total $0.20005. Plan discounts, platform usage and other applicable Apify charges are shown separately by Apify. Only confirmed dataset rows incur the result event; reports and failed-source diagnostics do not. Use the maximum total charge in Run options to bound costs. An unchanged-only run can have zero result charges while still incurring Actor Start/platform usage.

Default time budget is 60 seconds; allowed range is 30–120 seconds and the platform timeout can stop earlier. Each public request is limited to 20 seconds and 6 MiB, with public-address validation and no redirects. No new subscriptions, proxies or private credentials are required.

### Source and interpretation

[World Bank procurement dataset](https://datacatalog.worldbank.org/search/dataset/0037776/procurement-notice) · [Official procurement search](https://projects.worldbank.org/en/projects-operations/procurement) · [World Bank dataset terms](https://www.worldbank.org/ext/en/legal/terms-conditions/datasets).

Data source: World Bank. Follow the applicable dataset attribution and terms. This independent Actor is not affiliated with or endorsed by the World Bank. Source metadata can be delayed or inconsistent; inspect the original notice before making a bid decision. Questions or reproducible source changes can be reported through the Actor's Issues tab.

### Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

#### [EU Tenders Scraper - TED Notices, Deadlines & Contract Values](https://apify.com/maydit/eu-tenders-scraper)

Maintain separate international and European procurement shortlists in one research workflow.

1. Configure sector, geography and dates independently in each procurement tool.
2. Retain each portal's own notice ID, source URL, publication date and deadline when reviewing opportunities.

Similar titles do not establish duplicate contracts. A published notice can be informational, amended or expired; confirm eligibility and current documents at the source.

#### [Trade Policy Monitor - Export Controls & Rule Dates](https://apify.com/maydit/trade-policy-rule-monitor)

Add relevant trade-policy context when reviewing a cross-border supply opportunity.

1. Identify the actual jurisdictions and product categories involved in a notice.
2. Run a separate policy search and retain links and dates for qualified review.

This is research context, not an automatic legal or eligibility determination. A policy keyword match does not prove that a rule applies to a contract.

# Actor input Schema

## `noticeIds` (type: `array`):

Optional list of up to 10 OP notice IDs. Overrides keyword and project filters. Each selected notice is requested once; absent IDs are reported in SUMMARY, not billed as fake rows.

## `keyword` (type: `string`):

Optional World Bank full-text query, up to 120 characters. Searches the source notice, not only the exported title. Empty selects the source first window.

## `projectId` (type: `string`):

Optional exact project ID, such as P513815. Discovery verifies every returned project ID. Ignored when noticeIds is supplied.

## `maxResults` (type: `integer`):

1–100. Discovery requests one source window of this size. A smaller cap than an exact watchlist leaves the scope incomplete and prevents baseline updates.

## `maxRunSeconds` (type: `integer`):

Includes source requests, output and history. Platform timeout can stop earlier. Exact-ID requests are paced at least one second apart.

## `comparePrevious` (type: `boolean`):

Save exact source fields after complete selected-scope coverage. First run establishes a baseline; sequential runs with the same scope compare deadline, status and other fields.

## `onlyChanges` (type: `boolean`):

Implies comparison. Repeated unchanged observations may return zero records. Missing notices are not declared withdrawn or removed.

## `snapshotName` (type: `string`):

1–80 letters, digits, underscores or hyphens. IDs, search filters and window size also separate history. Run each snapshot sequentially.

## Actor input object example

```json
{
  "noticeIds": [],
  "keyword": "",
  "projectId": "",
  "maxResults": 3,
  "maxRunSeconds": 60,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `report` (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 = {
    "keyword": "",
    "maxResults": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/world-bank-procurement-notice-monitor").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 = {
    "keyword": "",
    "maxResults": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("maydit/world-bank-procurement-notice-monitor").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 '{
  "keyword": "",
  "maxResults": 3
}' |
apify call maydit/world-bank-procurement-notice-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maydit/world-bank-procurement-notice-monitor"
        }
    }
}
```

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/GkuziXDcnfYJXaNAq/builds/HsWT7S3nKlpLrP4pc/openapi.json
