# French Product Recall Monitor — RappelConso Alerts (`dalbian/product-recall-monitor`) Actor

Daily digest of official French product recalls from RappelConso: food, toys, vehicles, cosmetics and more, filtered by category, brand, risk, barcode or keyword, with the reason, the batches and the official notice.

- **URL**: https://apify.com/dalbian/product-recall-monitor.md
- **Developed by:** [Benjamin Jerez](https://apify.com/dalbian) (community)
- **Categories:** Business, News, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 search runs

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 Product Recall Monitor — RappelConso Alerts

Watch **RappelConso**, France's official product-recall register, and get every recall that matters to you: food, toys, vehicles, cosmetics, electrical goods, clothing and more — with the reason, the risk, the batches affected, what consumers are told to do, and a link to the official notice.

Set the window to one day and schedule it each morning, and it becomes a clean daily alert.

### What a recall looks like

| Field | Example |
| --- | --- |
| `productName`, `brand` | filet de poulet nature · sans marque |
| `category` / `subCategory` | alimentation / viandes |
| `risk` | salmonella spp |
| `reason` | détection de salmonella typhimurium |
| `batches` | 0096545118, date limite de consommation 20/09/2026 |
| `consumerAction` | ne plus consommer ; rapporter le produit au point de vente |
| `distributors`, `geographicScope` | the chains that sold it · france entière |
| `noticeUrl`, `posterUrl` | the official notice and the printable in-store poster |

### Filtering

**Categories** — alimentation, véhicules, jouets, hygiène-beauté, électroménager, vêtements and the rest. Matching is literal rather than full-text, which matters more than it sounds: a fuzzy search for *alimentation* also matches the category *bébés-enfants (hors alimentaire)* and hands you a toy. Here it does not.

**Brands** — watch your own products, or a supplier's.

**Risks** — listeria, salmonelles, E. coli, étouffement, blessure, chimique. Filter on the hazard rather than the product type when one risk is what concerns you.

**Barcodes** — check specific GTINs against the register. This is how a retailer verifies an assortment.

**Keywords** — free text across product name, brand and reason.

### Built for scheduling

The default window is seven days for a first look. Drop it to **one** and schedule the Actor daily: each run then returns only what appeared since yesterday, with no repeats to filter out.

An empty result on a given day is normal — the DGCCRF publishes on working days and some carry nothing. The summary row says which window it looked at, so a quiet day never looks like a broken run.

### Who uses this

Retailers and distributors checking whether anything on their shelves has been recalled. Food-service and catering operators with an obligation to act on withdrawal notices. Quality and compliance teams at manufacturers watching their own brands and their suppliers'. Consumer apps and price comparators. Insurers and journalists tracking product safety.

The `posterUrl` is worth knowing about: it links to the printable notice a shop is required to display, which turns an alert into an action a store manager can take immediately.

### Source and licence

**RappelConso**, published by the **DGCCRF** (Direction générale de la concurrence, de la consommation et de la répression des fraudes) through the public Opendatasoft catalogue, under the **Licence Ouverte**. Queried live on every run, never cached. No credentials.

### Frequently asked

**How fast does a recall appear here?**
As soon as the DGCCRF publishes it. The register carries a publication timestamp, and recalls appear through the working day rather than in one nightly batch.

**Does it cover recalls outside France?**
No. This is the French national register. European food and feed alerts circulate through RASFF, which is a separate system.

**What does `recallNature` mean?**
Whether the recall is voluntary or ordered by a prefectoral decree. Most are voluntary.

**Why do some recalls have no barcode?**
Because loose or unpackaged goods have none. `batches` then carries the lot number or use-by date instead, which is what the notice itself relies on.

# Actor input Schema

## `publishedWithinDays` (type: `integer`):

Only recalls published in the last N days. Set it to 1 and schedule the run each morning for a clean daily alert with nothing repeated. Leave it high for a first sweep of a category's history.

## `categories` (type: `array`):

Keep only these product categories, one per line — for example Alimentation, Véhicules, Jouets, Hygiène-Beauté, Électroménager, Vêtements. Matching is on the French labels the register uses, and partial words work.

## `brands` (type: `array`):

Keep only these brands, one per line. Use this to watch your own products, or a supplier's.

## `risks` (type: `array`):

Keep only recalls citing these risks, such as Listeria, Salmonelles, E. coli, blessure, étouffement, chimique. This is the field to filter on when one hazard matters more to you than the product type.

## `keywords` (type: `array`):

Free-text words searched across the product name, the brand and the reason for the recall, one per line. Combined with OR.

## `gtins` (type: `array`):

Check specific barcodes against the register, one per line. This is how a retailer verifies an assortment against everything recalled.

## `maxRecalls` (type: `integer`):

Cap per run, newest first. A daily run with sensible filters rarely returns more than a handful.

## Actor input object example

```json
{
  "publishedWithinDays": 7,
  "maxRecalls": 200
}
```

# Actor output Schema

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dalbian/product-recall-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("dalbian/product-recall-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 '{}' |
apify call dalbian/product-recall-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dalbian/product-recall-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/qDhwQe4Hsy7fDfJvx/builds/iHctPwHQZMMEtYbmX/openapi.json