# French Procurement Monitor (BOAMP, by CPV code) (`chosen_loafer/french-procurement`) Actor

Monitors new French public tenders (BOAMP notices) from boamp.fr, filtered by CPV code with deadline tracking. No personal data is collected.

- **URL**: https://apify.com/chosen_loafer/french-procurement.md
- **Developed by:** [Pavel Staurouski](https://apify.com/chosen_loafer) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 notice checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## French Procurement Monitor (BOAMP, by CPV code)

Monitors new French public tenders published on BOAMP (Bulletin Officiel des Annonces
de Marches Publics), filtered by CPV code and publication date.

### What you get

One record per matching tender notice: notice identifier, title, CPV codes (main and
additional, across all lots, deduplicated), response/submission deadline, publication
date, the contracting authority's name, the notice type, and a link to the official
notice page on boamp.fr. Nothing about named individuals.

### Sample output record

One real BOAMP notice (captured during testing), run through this Actor's own field
mapping (dates in ISO 8601; this particular notice's deadline has since passed, a live
run only ever returns notices inside your own date window):

```json
{
  "noticeId": "26-84547",
  "title": "Prestation d'entretien des espaces verts de la ville",
  "cpvCodes": ["77310000", "77341000", "77314000"],
  "deadline": "2026-09-29T15:00:00.000Z",
  "publicationDate": "2026-09-02T00:00:00.000Z",
  "publishingEntity": "Commune de Grigny",
  "noticeType": "Avis de marché",
  "link": "https://www.boamp.fr/pages/avis/?q=idweb:26-84547"
}
```

### What it does not do

No contact-person data, no attached tender documents, no full notice text beyond what
is needed to extract the CPV codes. Output is limited to structured tender metadata.
BOAMP's underlying notice data can include a named official (e.g. a mayor) alongside
an organisation's own contact details; this Actor never reads that part of the source
data for anything other than CPV codes, so it never reaches the output.

### Why you might need this

BOAMP publishes hundreds of French public tenders a day. Sub-EU-threshold French
tenders, the majority by count, never reach TED, so a procurement consultant or sales
team watching a specific CPV category has no feed to subscribe to beyond refreshing
the portal's own search by hand.

### Input

A list of CPV codes to watch, and optionally a publication date window.

```json
{
  "cpvCodes": ["45000000"],
  "publishedFrom": "2026-10-01",
  "publishedTo": "2026-10-31",
  "maxResults": 100,
  "maxChecked": 300
}
```

`maxChecked` is a safety cap on how many candidate notices get checked against your
CPV filter in this run (each check is billed, whether or not it matches). It stops the
run even if `maxResults` matches haven't been found yet, e.g. for a narrow CPV filter
with few matches in the date window.

CPV matching uses hierarchy prefixes: a filter of `45000000` (construction works,
division 45) matches a notice tagged `45214200` (school building construction) and
vice versa.

### Pricing

Pay per run started, plus per notice checked against your CPV filter (not just per
match: checking is the real cost driver). See the Pricing tab for exact rates.

***

### Moniteur des marches publics francais (BOAMP, par code CPV)

Surveille les nouveaux avis de marches publics francais publies sur le BOAMP (Bulletin
Officiel des Annonces de Marches Publics), filtres par code CPV et date de publication.

Ce que vous obtenez : un enregistrement par avis correspondant, avec l'identifiant de
l'avis, le titre, les codes CPV (principal et complementaires, tous lots confondus,
sans doublon), la date limite de reponse, la date de publication, le nom de l'acheteur
public, le type d'avis et un lien vers l'avis officiel sur boamp.fr. Aucune donnee
concernant des personnes nommees.

Ce que cet outil ne fait pas : aucune donnee de personne de contact, aucune piece
jointe du dossier de consultation, aucun texte integral de l'avis au-dela de ce qui est
necessaire pour extraire les codes CPV. Les donnees source du BOAMP peuvent contenir le
nom d'un elu (par exemple un maire) a cote des coordonnees de l'organisme ; cet outil ne
lit jamais cette partie des donnees source pour autre chose que les codes CPV, elle
n'apparait donc jamais dans le resultat.

Pourquoi : le BOAMP publie plusieurs centaines d'avis par jour. Les marches publics
francais sous les seuils europeens, qui representent la majorite en nombre, ne sont
jamais transmis au JOUE (TED), donc un consultant en marches publics ou une equipe
commerciale qui surveille une categorie CPV donnee n'a aucun flux auquel s'abonner, en
dehors de rafraichir manuellement la recherche du portail.

Tarification : paiement par execution demarree, plus par avis verifie par rapport a
votre filtre CPV (pas seulement par correspondance trouvee : la verification est le
veritable cout, pas la correspondance). Voir l'onglet Tarification pour les tarifs
exacts.

# Actor input Schema

## `cpvCodes` (type: `array`):

List of CPV codes to monitor, e.g. \["72000000", "45000000"]. Matches hierarchically against the main and additional CPV codes on each notice.

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

ISO date (YYYY-MM-DD). Only notices published (dateparution) on or after this date are returned. Defaults to 30 days ago.

## `publishedTo` (type: `string`):

ISO date (YYYY-MM-DD). Only notices published on or before this date are returned. Defaults to today.

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

Maximum number of matching tender records to output.

## `maxChecked` (type: `integer`):

Safety cap on how many candidate notices are checked against your CPV filter in this run (each check is a billed event, regardless of match). Stops the run even if "Max results" matches haven't been found yet, e.g. for a narrow CPV filter with few matches in the date window.

## Actor input object example

```json
{
  "cpvCodes": [
    "72000000"
  ],
  "maxResults": 100,
  "maxChecked": 300
}
```

# Actor output Schema

## `matchedTenders` (type: `string`):

Per-tender records.

# 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 = {
    "cpvCodes": [
        "72000000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("chosen_loafer/french-procurement").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 = { "cpvCodes": ["72000000"] }

# Run the Actor and wait for it to finish
run = client.actor("chosen_loafer/french-procurement").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 '{
  "cpvCodes": [
    "72000000"
  ]
}' |
apify call chosen_loafer/french-procurement --silent --output-dataset

```

## MCP server setup

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

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/64rpyWGfXR2XXtJvU/builds/YePBC8MUZeq4ogSMp/openapi.json