World Bank Procurement Notice Change Monitor avatar

World Bank Procurement Notice Change Monitor

Pricing

from $1.20 / 1,000 saved observations

Go to Apify Store
World Bank Procurement Notice Change Monitor

World Bank Procurement Notice Change Monitor

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.

Pricing

from $1.20 / 1,000 saved observations

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Features

Limited permissions

Share

World Bank Procurement Notice Change Monitor — illustrative workflow

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:

{"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.

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

Track two infrastructure notices

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

{
"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.

{
"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

FieldMeaning
noticeId, projectIdSource OP notice and P project identities
title, noticeType, noticeStatusSource description, notice class and reported status
countryName, buyerOrganizationPublished country label and institutional buyer; optional in source
bidReference, procurementMethodCodeSource procurement reference/method when supplied
noticeDateRaw, noticeDateRaw publication label and recognized calendar date
deadlineDateRaw, deadlineTimeRawOriginal source deadline values, not normalized to a guessed timezone
deadlineChanged, statusChangedComparison flags; null before a prior comparable observation exists
comparisonStatus, changedFields, previousExact saved-observation comparison evidence
sourceUrl, observedAtOfficial 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 · Official procurement search · World Bank dataset terms.

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

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

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.