# African Development Bank Procurement Scraper (`publicmoney/afdb-procurement-scraper`) Actor

Extract African Development Bank project procurement notices: title, publication date, notice type, country, sector, project code, description and notice documents.

- **URL**: https://apify.com/publicmoney/afdb-procurement-scraper.md
- **Developed by:** [Public Money](https://apify.com/publicmoney) (Apify)
- **Categories:** Business
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $1.00 / 1,000 tenders

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

This Actor reads the African Development Bank's project procurement notices from `www.afdb.org/en/projects-and-operations/procurement`: general and specific procurement notices, requests for expressions of interest, invitations for bids, procurement plans and contract awards. It returns one record per notice.

### Source

- Listing: `https://www.afdb.org/en/projects-and-operations/procurement`, 18 notices per page, `?page=<n>` from 0, newest first. About 694 pages (roughly 12,500 notices) on 2026-10-04.
- Notice page: `https://www.afdb.org/en/documents/<slug>` for the notice type, tags, body and attached files.
- The site is behind Cloudflare. The Actor reads it directly and falls back to Apify's `UNBLOCKER` proxy group when the direct read gets the challenge page.

### Input

| Field | Type | Default | What it controls |
| --- | --- | --- | --- |
| `keyword` | string | empty | AfDB's own Title filter (title contains the text), server-side |
| `country` | string (select) | empty | AfDB's own Country filter, server-side |
| `sector` | string (select) | empty | AfDB's own Sector filter, server-side |
| `publishedFrom` | date | empty | Stops at the first notice published before this date |
| `maxPages` | integer | `5` | Listing pages to walk, 18 notices each |
| `fetchDetails` | boolean | `true` | Opens each notice page for the fields marked below |
| `maxItems` | integer | `500` | Caps the records returned; `0` for no cap |
| `schemaOrg` | boolean | `false` | Appends a schema.org block to each record |

```json
{
    "country": "352",
    "publishedFrom": "2026-09-01",
    "maxItems": 100
}
```

### Output

| Field | From | Notes |
| --- | --- | --- |
| `title` | listing | |
| `publicationDate` | listing | `YYYY-MM-DD`; null on the oldest notices, which AfDB lists undated |
| `noticeType` | notice page | Document category, e.g. Request for Expression of Interest, Invitation for Bids, Procurement plans, Contract Awards to Consultants |
| `categories` | notice page | Every category tag, including the umbrella "Project-related Procurement" |
| `projectCode` | notice page | AfDB project code, e.g. `P-TG-K0-009`; null when the notice links none |
| `keywords` | notice page | Country, sector and topic tags; AfDB does not mark which is the country |
| `description` | notice page | Body text |
| `documents` | notice page | Attached notice files (PDF, XLSX) |
| `lastUpdated` | notice page | As printed, e.g. `02-Oct-2026` |
| `nodeId` | notice page | AfDB's node id |
| `noticeUrl` | listing | |
| `scrapedAt` | run | |

### Gotchas

- AfDB orders notices published on the same day differently on every request. A notice can therefore show up on two adjacent pages of one walk, and another can slip between them. The Actor drops the repeat within a run (2 pages: 36 rows, 33 distinct on 2026-10-04); it cannot recover a notice the site moved past the page boundary.
- Notice titles and bodies are in the language AfDB published them in, mostly English or French.
- The listing has no date filter; `publishedFrom` works because the listing is newest first.

# Actor input Schema

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

Sent to AfDB's own Title filter, which matches notices whose title contains the text. Examples: 'Kenya', 'audit', 'PPM'. Leave empty for every notice.

## `country` (type: `string`):

AfDB's own Country filter. Leave empty for every country.

## `sector` (type: `string`):

AfDB's own Sector filter. Leave empty for every sector.

## `publishedFrom` (type: `string`):

Only notices published on or after this date (YYYY-MM-DD). The listing is newest first, so the run stops at the first older notice. Notices AfDB publishes without a date are skipped when this is set.

## `maxPages` (type: `integer`):

Listing pages to walk. Each page holds 18 notices. Examples: 1, 5, 700. Default is 5.

## `fetchDetails` (type: `boolean`):

Opens each notice to add its notice type, country, sector, project code, description, last-updated date and document links. Off returns only the title, link and publication date from the listing.

## `maxItems` (type: `integer`):

Maximum number of records to return. 0 returns everything matched. Examples: 1, 500, 2000. Default is 500.

## `schemaOrg` (type: `boolean`):

Appends a `schemaOrg` object to the end of every record, mapping it to schema.org (Demand for tenders, MonetaryGrant for grants, Invoice for payments). The record's own fields are not changed. Off by default. Charged once per run, not per record.

## Actor input object example

```json
{
  "maxPages": 5,
  "fetchDetails": true,
  "maxItems": 500,
  "schemaOrg": false
}
```

# Actor output Schema

## `results` (type: `string`):

Procurement notices matched by the run, one item per record, in the default dataset.

# 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 = {
    "maxPages": 5,
    "maxItems": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("publicmoney/afdb-procurement-scraper").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 = {
    "maxPages": 5,
    "maxItems": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("publicmoney/afdb-procurement-scraper").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 '{
  "maxPages": 5,
  "maxItems": 500
}' |
apify call publicmoney/afdb-procurement-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,publicmoney/afdb-procurement-scraper"
        }
    }
}
```

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/vJX4TBr6OKf2FggZi/builds/dlag5sJJS26Zf1EYS/openapi.json