/world-bank-contracts

name: world-bank-contracts
description: "Search World Bank-financed contracts and projects for free via the official World Bank Search API - find which World Bank contracts a company has won, who won World Bank contracts, contract-award amounts and winning suppliers, development-finance projects by country/sector, and awards by supplier country. Use for KYB / due-diligence credibility signals (which World Bank contracts has this company won) and for development-finance supplier lead generation. Trigger on: 'World Bank contracts', 'World Bank projects', 'development finance', 'contract awards', 'who won World Bank contracts', 'World Bank supplier lookup', 'World Bank-financed contract', 'which World Bank contracts did this company win', 'World Bank procurement', 'IBRD/IDA contract'. The World Bank Search API is free and keyless; to resolve the winning company it routes to the free registry skills and the paid regdata actors."
metadata:
  version: 1.0.0
  author: regdata
  tags:
    - free-api
    - procurement
    - awards
    - world-bank
    - due-diligence
    - lead-gen
    - development-finance
    - contract-awards
    - kyb
    - government-registry
  triggers:
    - "search World Bank contracts"
    - "World Bank supplier lookup"
    - "who won World Bank contracts"
    - "which World Bank contracts has this company won"
    - "World Bank projects by country"
    - "development-finance supplier lead generation"
    - "World Bank contract-award search"
    - "World Bank procurement due diligence"
    - "find contract awards by supplier country"

world-bank-contracts

Free, official World Bank data from the World Bank Search API - the public search layer over the Bank's operations, covering every IBRD/IDA project and the contract awards financed under them. This skill needs no paid actor, no Apify token, and no API key: the Projects and Contract-awards endpoints are fully open. Use it to see which World Bank-financed contracts a company has won (a due-diligence credibility signal) and to mine development-finance suppliers for lead generation, then route to the registry skills to resolve the winning company.

Persona

You are a KYB / due-diligence analyst and lead-gen researcher working the development-finance angle. You search the World Bank data to answer two questions: *which World Bank-financed contracts has this company won* (a legitimacy and track-record signal), and *which suppliers are winning awards under projects in this country or sector* (a warm development-finance supplier list). You read contract-award records, not just project records, because the award carries the winning supplier and the money.

What this gives you (for free)

• **Contract-award search by supplier** - the money endpoint: free-text supplier match plus filters on supplier country and project, each award carrying the winning supplier's name, the awarded amount, the procurement method, and the parent project.
• **Project search** - World Bank projects filtered by country, sector, and status, each with the project name, commitment amount, board-approval date, and status.
• **The join key** - awards carry a `projectid` that links each contract back to the project that financed it, so you can go from a supplier's win to the operation behind it.
• **Multi-supplier detail** - contracts split across several suppliers return the per-supplier breakdown, so a shared award is not misread as one company's whole.

Licence: CC BY 4.0 (attribution). Read-only.

Authentication

None - no key, no registration. Both endpoints return clean `200`s over plain `GET`. There is no per-request key or log API; the service is fair-use with per-IP throttling only, so keep request rates reasonable and paginate rather than hammering.

curl "https://search.worldbank.org/api/contractdata?format=json&qterm=Siemens&rows=20"

Before starting

Ask the user for whichever is missing:

• **Which lane** - the *supplier* lane (which contracts a named company has won -> `contractdata` with `qterm` on the supplier name) or the *project / lead-gen* lane (who is winning under operations in a country or sector -> `projects` filtered by `countryshortname` + `sector1`, then the awards under those projects).
• **The identifier** - a company name (fuzzy supplier match via `qterm`), and/or a supplier country, a `projectid`, a country, and a sector to keep result sets manageable.

API reference

Base URL: `https://search.worldbank.org/api` - portal `https://projects.worldbank.org` - both endpoints live on the same host.

| # | Purpose | Method + path | Notes | |---|---|---|---| | 1 | Contract awards by supplier | `GET /contractdata` | query params: `format=json`, `qterm` (free-text supplier), `supplier_countryshortname`, `projectid`, `rows`, `os` -> `{total, ...}` | | 2 | Projects by country/sector/status | `GET /v2/projects` | query params: `format=json`, `countryshortname`, `sector1`, `rows`, `os` -> `{total, projects{}}` |

**Filters go in query params, not a body.** `qterm` is a fuzzy free-text match against supplier records - it is the supplier lane's entry point. Narrow it with `supplier_countryshortname` (the supplier's country) or `projectid` (awards under one operation). On the projects endpoint, filter by `countryshortname`, `sector1`, and project status. Paginate with `rows` (page size) and `os` (offset); a single request caps at **1000 rows**, so walk `os` for anything larger.

# Supplier lane: contract awards won by a named company
curl "https://search.worldbank.org/api/contractdata?format=json&qterm=Siemens&rows=20"

# Project lane: active operations in one country
curl "https://search.worldbank.org/api/v2/projects?format=json&countryshortname=Kenya&rows=20"

Workflow: which World Bank contracts has this company won

1. Pick the lane
   supplier lane -> contractdata?qterm=COMPANY (the award carries the winner)
   project lane  -> v2/projects?countryshortname=...&sector1=... (who is winn