# FDA & FSA Food Recalls for Importers (`prixodik/fda-fsa-food-recalls`) Actor

Collect US FDA and UK FSA food recall notices in one English schema. Filter by keyword and publication date, preserve lot details, and track new or changed records.

- **URL**: https://apify.com/prixodik/fda-fsa-food-recalls.md
- **Developed by:** [Milchenko Oleksii](https://apify.com/prixodik) (community)
- **Categories:** Business, E-commerce
- **Stats:** 2 total users, 1 monthly users, 94.4% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

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

## FDA & FSA Food Recalls for Importers

Collect US FDA and UK FSA food recall notices in one English schema. Filter by keyword and publication date, preserve lot details, and track new or changed records.

Built for food importers and internal quality teams working with both the United States and the United Kingdom. One workflow, a consistent schema, exact source identifiers and original product/lot details. This Actor does not determine whether a notice applies to your goods.

### Quick start

Run the Actor using the Input tab or API. Example:

```json
{ "maxRecords": 50, "maxPages": 3, "mode": "snapshot", "query": "", "countries": [], "dateFrom": "" }
```

No FDA/FSA API key, browser, proxy or external AI service is required for the default food sources. Export the dataset as JSON, CSV or Excel using Apify.

### Input

| Field | Meaning |
|---|---|
| maxRecords | Maximum valid records inspected per source before filtering; 1-1000. |
| maxPages | Maximum pages per source; 1-10. The recipe defines each page's size. |
| mode | snapshot returns all matches; changes returns new or changed records. |
| query | A literal case-insensitive phrase in the record name or fields; empty disables this filter. |
| countries | US and/or GB for food recalls; an empty list selects both. |
| dateFrom | Minimum publication date, YYYY-MM-DD; empty disables this filter. |
| stateStoreId | A separate named Apify key-value store for each recurring task. Required for changes mode. |
| records | Input objects for transformer Actors only, with id, name and mapped fields. |

Filters are applied inside the inspected window. A zero-result search does not prove that no notice exists elsewhere. The current food recipe reads 20 records per page; ten pages inspect at most 200 records per source. This is a bounded monitoring/export tool, not a complete historical archive downloader.

### Output

One dataset row is one official notice or source record. Different agencies and recall numbers are never merged by similar names. Records have id, name, fields, origins and change. English food fields include country (US/GB), agency, recallNumber, title, publishedAt, modifiedAt, company, classificationOriginal, statusOriginal, reasonOriginal, batchesOriginal, productsOriginal, structuredAllergens, sourceUrl, license and attribution. FDA modifiedAt is null; source-specific classifications are kept as published. Missing values remain null or empty arrays. Original lot and product text is preserved.

Example shape (illustrative values):

```json
{ "id": "stable-source-id", "name": "Example food recall", "fields": { "country": "US", "agency": "FDA", "recallNumber": "EXAMPLE-001", "publishedAt": "2026-10-01", "company": "Example supplier", "sourceUrl": "https://api.fda.gov/food/enforcement.json", "license": "https://open.fda.gov/license/" }, "origins": [{ "sourceId": "fda", "originalId": "EXAMPLE-001", "url": "https://api.fda.gov/food/enforcement.json", "observedAt": "2026-10-01T00:00:00Z" }], "change": "new" }
```

### Recurring use

Use the same stateStoreId and semantic filters for sequential runs. Run a baseline with snapshot mode and the named store, then switch to changes. If you use changes immediately, the first run establishes the baseline by returning all matching records. Do not run the same state store concurrently. State is saved only after dataset delivery; undelivered records are not marked as already seen. State history is limited to 50,000 IDs. Absence from a later window does not mean deletion or recall closure.

### Pricing proposal

Pay per event: **$0.01 per Actor start + $1.5 per 1,000 delivered records** ($0.0015 each). A run returning 100 records costs $0.16; a run returning 10 costs $0.025; a run returning no records may incur the $0.01 start fee. No monthly rental. Platform usage is intended to be included.

One result is one official notice or source record successfully delivered to the dataset. Multiple products and lots within a notice are not billed separately. Snapshot mode bills every delivered record on each run; changes mode bills only newly delivered or changed records. Unchanged and filtered-out records do not incur a result fee. The Actor-start fee may apply to empty or failed runs. No monthly subscription or third-party API fee is required. Proposed pricing includes platform usage; activation must be confirmed in Apify Console.

**This is the prepared tariff, not proof of active billing. Always check the Pricing tab in Apify for the effective price before running.** Apify applies your maximum run cost. The SDK limits dataset delivery to the available event budget; records not delivered because of that limit remain eligible for a later changes run.

### Reliability and limitations

Required-source failures fail the run without saving new state. Optional-source failures are listed in SUMMARY warnings. Only temporary network errors are retried; request count, response size, runtime and memory are bounded. Invalid source records missing an ID or name are skipped and counted. SUMMARY reports examined, matched, delivered, invalid, duplicates, pages, bytes, durationMs, bounded, chargeLimitReached and warnings.

FDA enforcement data is updated weekly after classification. Its original status is not maintained as the recall lifecycle progresses. Do not use openFDA enforcement data for public alerts, emergency decisions or to infer closure. FSA modified dates support content-change tracking. No safety certification, legal opinion, recall applicability decision, or guarantee of archive completeness is provided. Consult the original notices and your qualified compliance staff.

### Sources and attribution

- FDA/openFDA food enforcement reports: https://open.fda.gov/apis/food/enforcement/ . FDA/openFDA data under the applicable public-domain/CC0 terms: https://open.fda.gov/terms/ .
- Food Standards Agency food alerts: https://data.food.gov.uk/food-alerts/ui/reference . Contains Food Standards Agency information licensed under the Open Government Licence v3.0: https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/ .

This Actor is independently maintained and is not endorsed by FDA or FSA. Report reproducible problems in the Actor Issues tab with the run ID and input, without credentials.

### Run output links

The Output tab provides Results from the default dataset and Run summary from the SUMMARY record in the default key-value store. The output schema is declared in .actor/output_schema.json.

# Actor input Schema

## `maxRecords` (type: `integer`):

Maximum valid records inspected per source before filtering.

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

Limit the inspected window. Archive completeness outside it is not guaranteed.

## `mode` (type: `string`):

All matches, or only new and changed records since a successful run.

## `query` (type: `string`):

A literal case-insensitive phrase in the record name or fields. Empty disables filtering.

## `countries` (type: `array`):

Food recalls only: US and/or GB. Empty selects both.

## `dateFrom` (type: `string`):

Minimum publication date in YYYY-MM-DD format. Empty disables filtering.

## `stateStoreId` (type: `string`):

A separate named key-value store for each task. Required in changes mode. Run sequentially.

## `records` (type: `array`):

Transformer Actors only: objects with id, name and mapped output fields.

## Actor input object example

```json
{
  "maxRecords": 50,
  "maxPages": 3,
  "mode": "snapshot",
  "query": "",
  "countries": [],
  "dateFrom": "",
  "records": []
}
```

# Actor output Schema

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

Records delivered to the default dataset.

## `summary` (type: `string`):

Collection statistics, delivery limits and source warnings.

# 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("prixodik/fda-fsa-food-recalls").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("prixodik/fda-fsa-food-recalls").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 prixodik/fda-fsa-food-recalls --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,prixodik/fda-fsa-food-recalls"
        }
    }
}
```

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/a6wHBKVJqhtBTekEc/builds/JTrvRM0hbsXdjdwPP/openapi.json