EU Product Recall Data API

Turn EU recall alerts into a queryable, monitorable data API.

Based on EU Safety Gate (RAPEX) public alerts, we organise fields such as product name, brand, risk type and alert date, with Chinese keyword search and structured JSON responses for product compliance screening and supply chain risk monitoring.

No need to crawl alert websites country by country yourself.

View API Docs

Enterprise solution enquiryJSON APIStatic demo snapshot

All alertsToysElectrical appliancesClothing

Input

1 Product name e.g. Electric grinder

Query target: Product

2 Brand e.g. Yearninglife

Query target: Brand

3 Alert number e.g. SR/02255/26

Query target: Number

Result preview

The sample is a demo data snapshot; enter a keyword to filter instantly and click an entry for details.

367 alertsAlerts collected

15 categoriesRisk type

9Product categories covered

2025–2026Data time range

Recall alert search

Static demo · sample data snapshot (collected 2026-08-25). Enter a keyword or pick filters, then click a card to view alert details.

Keyword search

Product category

Risk type

Brand

Results:0 alerts

Sort

Between public alerts and business-ready data lie collection, translation and structure.

The real problem is not whether you can find the alert, but whether alerts scattered across sites, in different languages with inconsistent fields, can go straight into your business systems.

Recall record sample Raw alerts vs structured results

001SR/02255/26Alert number

002Electric grinderProduct name

003Electric shock / cut injuryChinese risk labelling

Structured response JSON Product · brand · risk · date

01
Alerts are scattered and hard to track
Alerts from each country live on different public pages, so refreshing manually every day easily misses records relevant to your products — by the time the platform notifies you, the product has already been delisted.
02
Language and terminology barriers
Most alerts are written in the local EU language, so product names and risk descriptions need translating; manual organisation is expensive and prone to misinterpretation.
03
Risk levels are not intuitive
Alert fields are scattered, making it hard to filter and sort quickly by risk type, so prioritisation relies on human judgement.
04
Self-built collection is hard to maintain
Page structure changes, access restrictions and field changes all need continuous attention, and the maintenance cost exceeds most small and mid-sized teams’ budgets.

From EU public alerts to queryable data in six processing stages

An alert passes through collection, cleaning, standardisation, classification, linking and delivery to become a structured JSON result.

Collect

Fetch alerts from the public EU Safety Gate pages

eu.safety_gate.fetch()

Clean

Removes duplicate alerts and fixes malformed fields

parse · dedupe

Normalize

Unifies product name, brand, date and alert number

schema.map()

Classification

Classifies products and risks by category rules and keywords

category.guess()

Relate

Links multiple alerts and risk fields for the same product

record.join()

Deliver

Returns structured JSON data over a REST API

json_api.v1

You don't have to maintain collection and cleaning pipelines yourself.Call the API and get structured results directly.

Recall search and monitoring, covering the core product compliance use cases

Unified REST API · JSON responses. The recall search endpoint is the planned core, with brand monitoring built on the same data structure. All responses below are static demo samples.

Recall alert search API

Query recall records by product, brand or alert number

Enter a product name, brand, alert number or date range to get matching recall records including risk type, alert date and alert number. Chinese keyword search is supported, and risk types are labelled in Chinese.

Product name
Brand
Risk type
Alert number
Alert date

Product selection review · supplier screening · product compliance due diligence · alert record search

GET /v1/recall/query

Static demo · Sample response200 OK

{
  "code": 0,
  "message": "success",
  "data": {
    "alert_number": "SR/02255/26",
    "product": "Electric grinder",
    "brand": "Yearninglife",
    "category": "Electrical appliances/Electronics",
    "risks": ["Electric shock", "Cut injury"],
    "notified_date": "2026-08-24",
    "report": "Weekly report"
  }
}

Brand recall monitoring API

Set brand or product rules and get notified when an alert matches

Set monitoring rules by brand, category or product name; when a new alert matches, you are notified by Webhook or WeCom, reducing manual polling. This capability is planned — ask your consultant about the integration approach.

Monitoring rules
Match notification
Webhook
WeCom

Continuous supply chain monitoring · in-market product tracking · risk alerts

POST /v1/recall/subscribe

Static demo · sample response (planned)200 OK

{
  "code": 0,
  "message": "success",
  "data": {
    "rule_id": "sub_20260825_001",
    "monitor_brand": "Yearninglife",
    "notify_channel": "webhook",
    "status": "Created"
  }
}

Recall data can flow into your real business processes

Not another back office to open, but recall records where product selection, procurement, review and risk control actually happen.

Cross-border e-commerce product selection

Check historical alerts for the same or similar products before listing, and build recall records into product selection review.

Product nameRecall alert search APIProduct selection reference

Importers and brand owners

Screen supplier and brand alert history before purchasing to reduce manual lookups.

BrandRecall alert search APISupplier screening

Testing and certification bodies

Integrate alert data into compliance analysis reports instead of crawling each site manually.

Alert numberRecall alert search APIAnalysis reports

ERP / SaaS platforms

Integrate recall data into ERP and risk systems as a product compliance reference field.

Brand / categoryRecall alert search APISystem integration

Supply chain teams

Bulk-screen supplier product alerts by category and feed them into supplier due diligence.

CategoryRecall alert search APIDue diligence process

Alerts cluster in toys and electrical appliances, with choking and electric shock the main risks

The statistics below are based on the 367 alerts in the current demo data snapshot. They are static and illustrative only, and do not represent the full set of EU alerts.

Alerts collected: 367 alerts
Categories covered: 9
Risk type: 15 categories
Data status: Static demo
Statistics date: 2026-08-25
Date range: August 2025 – August 2026

Risk and category distribution in the current snapshot

Top risk 1: choking hazard, 105 alerts
Top risk 2: electric shock, 73 alerts
Top risk 3: chemical risk, 71 alerts
Top category 1: toys, 158 alerts
With brand recorded: 225 alerts
Scope: current demo snapshot

The value of an API is more than "returning the alerts to you"

GooFuture's core value comes before the query: collecting, cleaning, classifying and translating scattered public alerts into Chinese so the results can be used directly in business.

Collect

Structured collection

Collects alerts from the public EU Safety Gate pages and organises them into structured fields.

Web page text → JSON fields

Classification

Category classification

Automatically classifies products into categories such as toys or electrical appliances based on product name keywords.

Uncategorised → category tags

Risk

Risk translation

Translates English risk types into Chinese for non-English-speaking teams.

English source → bilingual comparison

Relate

Alert linking

Links alert number, brand and date fields for the same product.

Scattered records → linked records

Deliver

API-first

Call it on demand over REST API with JSON responses — no need to build your own collection pipeline.

Manual lookup → API calls

From enquiry to your first API call in just three steps

Code and responses are static samples. Your consultant will propose an integration plan based on data scope, call volume and delivery method.

01
Contact a consultant
Scan the QR code to add us on WeCom and tell us your business scenario, the data scope you need and your expected call volume.
02
Confirm the plan
Confirm data coverage, update frequency, endpoint scope and enterprise support needs.
03
Start integration
Get the integration documentation and sample data, then wire the structured JSON results into your ERP, SaaS or business system.

cURLResponse

curl -X GET "https://api.goofuture.com/v1/recall/query?keyword=grinder" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

Static demo · JSON response200 OK

{
  "code": 0,
  "data": {
    "total": 1,
    "product": "Electric grinder",
    "risks": ["Electric shock", "Cut injury"]
  }
}

From testing to production

Choose a plan by call volume, data coverage and enterprise support. Your consultant quotes based on your business needs.

Basic

For API testing and product validation

Contact a consultant

Monthly requests: 1,000
Core endpoints: Recall search
Rate limits: Basic rate limiting
Data coverage: Sample snapshot

Standard

For individual developers and small teams

Contact a consultant

Monthly requests: 50,000
Core endpoints: Recall search
Category filter: Support
Chinese risk label: Support

Recommended plan

Professional

For ERP / SaaS platforms

Contact a consultant

Monthly requests: 500,000
Brand monitoring: Planned
Bulk checks: Support
Update frequency: As per the agreed plan

Enterprise

For platforms, data companies and large enterprises

Contact a consultant

Monthly requests: High-volume usage
Custom data scope: Negotiable
Private deployment: Negotiable
Technical support: Enterprise technical support

The questions worth confirming before integrating a recall data API

Straight answers on data sources, update frequency, query conditions and commercial integration.

Why not just search the EU Safety Gate website?

The EU Safety Gate website is searchable, but its page structure and languages are EU-centric, so bulk queries, Chinese search and structured responses all need extra work. GooFuture handles collection, cleaning and classification centrally and delivers structured results via API, cutting manual effort.

Where does the data come from?

Sourced from EU Safety Gate (RAPEX) public alerts. GooFuture collects, cleans and labels the alerts in Chinese as a third-party data processing service, and is not affiliated with the European Commission.

How often is it updated?

This page is a static demo snapshot (collected 2026-08-25) and the data status is shown on the page. The production API update frequency is agreed in your integration plan — confirm during consultation.

Which query filters are supported?

Filter by product name, brand, alert number, risk type, category and date range; exact behaviour is per the formal API documentation. Risk types in the sample data are translated into Chinese.

Do you support Chinese search?

Yes. Risk types in the sample data are translated into Chinese while product names and brands keep their original form, so you can query with Chinese or source-language keywords.

Can it be integrated into ERP or SaaS?

Yes. The API follows REST design and returns JSON, so it can plug into e-commerce ERP, risk systems and compliance workflows; commercial usage is governed by the applicable plan and service agreement.

How can it be used for cross-border product selection or supplier due diligence?

Query historical alerts by product name, brand and category before listing or purchasing, and use recall records as a reference field in product selection and supplier review to reduce manual work.

How is it billed and how do I choose a plan?

Choose a plan by endpoint scope, call volume and update frequency; your consultant quotes based on your business needs, with no public pricing on this page.

No more maintaining a per-country alert collection pipeline.

From collection and cleaning to classification and labelling — we handle it all. Your systems just call the API.

Enterprise consultant onboarding · JSON API · static demo snapshot

EU Product Recall Data API

Input

Result preview

Alerts are scattered and hard to track

Language and terminology barriers

Risk levels are not intuitive

Self-built collection is hard to maintain

Collect

Clean

Normalize

Classification

Relate

Deliver

Recall alert search API

Brand recall monitoring API

Cross-border e-commerce product selection

Importers and brand owners

Testing and certification bodies

ERP / SaaS platforms

Supply chain teams

Risk and category distribution in the current snapshot

Structured collection

Category classification

Risk translation

Alert linking

API-first

Contact a consultant

Confirm the plan

Start integration

No more maintaining a per-country alert collection pipeline.