US CPSC Recall Data API

Plug decades of US consumer product recall records straight into your business systems.

We continuously collect and process CPSC public data, cleaning, deduplicating, entity-normalising and relationship-modelling company names, products, UPCs, hazards and remedies.

No need to crawl, clean and maintain the data yourself.

View API Docs

Enterprise solution enquiryJSON APIBearer token authentication

OverviewName variants (3)Recall records (—)Products (—)Hazards (—)

Input name variant 3

1 Target Name variants

Data source: CPSC recall notices
First seen: —

2 Target Corp. Name variants

Data source: CPSC recall notices
First seen: —

3 Target Corporation Name variants

Data source: CPSC recall notices
First seen: —

Master company entity normalised

TARGET
CORPORATION

Company entity ID: —
Entity type: —
Region: —
Status: —
Normalised name: TARGET CORPORATION
Parent entity: —
Headquarters: —
First seen: —
Last confirmed: —

9,962+Official recall records

From 1973 to todayHistorical data coverage

18,229Company entity consolidation

Updated dailyContinuous public data sync

The public data is free to download, but it is far from being "ready for business use".

The real problem isn't whether the data exists, but how to turn raw notices into data your business systems can query, link and monitor continuously.

Original company name Public data source

001TargetSource value

002Target Corp.Source value

003Target CorporationSource value

Company entity normalisation TARGET CORPORATION Merged into a single company entity

01
Data is scattered
Products, companies, hazards, UPCs and remedies are deeply interconnected and must be restructured before they can be queried in a business system.
02
Inconsistent company names
The same company may appear under several names; naive counting inflates duplication, misses links and distorts trends.
03
Hard to monitor continuously
Companies need to know continuously whether new recalls appear for the companies, brands or products they care about — not just check manually once in a while.
04
Maintenance costs keep piling up
Crawling, field changes, outliers, sync failures and data pipelines all demand long-term engineering resources.

From public data to a directly callable commercial data API

A raw record passes through six auditable stages to become stable, structured, linkable JSON.

Collect

Continuous collection of official CPSC recall data

source.capture()

Clean

Cleans outliers, format differences and duplicate records

parse · dedupe

Normalize

Unifies company, country, date, product and hazard fields

schema.map()

Entity resolution

Identifies and merges name variants of the same company

entity.match()

Relate

Links products, companies, UPCs, hazards and remedies

graph.link()

Deliver

Delivered to your systems through a stable REST API

json_api.v1

You don't have to maintain crawlers, databases or cleaning pipelines.Call the API and use the results directly.

One API covering the core recall data use cases

Unified REST API · JSON responses · Bearer token authentication. Company records and recall search are the core of the product, with the other capabilities built on the same data model.

Company recall record API

Supplier and company due diligence

Enter a company name to get historical recall records, products involved, frequent hazards, remedies, countries of manufacture and recall trends. Supports fuzzy name matching and entity normalisation.

Historical recall count
First / latest recall
Products and hazards
Country of manufacture
Trend and risk metrics

Supplier due diligence · company background checks · importer risk control · procurement review

GET /v1/company/profile?name=Anker

Static demo · Sample response200 OK

{
  "query": "Anker",
  "entity": {
    "normalized_name": "Anker Innovations",
    "aliases": ["—"],
    "recall_summary": {
      "total": null,
      "latest": null
    }
  },
  "source": "U.S. CPSC"
}

API 02

Product recall search API

Search historical recall records by product keyword, model, UPC, country of manufacture, hazard type and date range.

GET /v1/recalls/search?q=cordless+drill JSON

New product listing checkCheck recall records for similar products

UPC lookupExact match when a barcode is present

Product researchAnalyse historical safety issues by category

API 03

Recall detail API

Complete structured data for a single recall event, for compliance systems, archiving, internal review and research.

GET /v1/recalls/{recall_id} Official title · date · company role · incidents and injuries · UPC · remedy

API 04

CPSC recall monitoring API

Set up continuous monitoring by company, brand, product keyword, category, UPC or country of manufacture.

POST /v1/monitors Email notifications · Webhook · brand and supply chain monitoring

API 05

Recall analytics API

Get annual trends, country-of-manufacture distribution, company rankings, frequent hazards and remedy aggregations.

GET /v1/analytics/trend?country=China Industry research · risk models · market analysis · report generation

This data can flow into your real business processes

Not another back office to open, but recall intelligence where procurement, listings, supplier review and product research actually happen.

Cross-border e-commerce

Screen for product recalls before listing or purchasing, checking the recall history of the product and its supplier.

Product SKURecall search APIMatched / unmatched

Importers / brand owners

Add company recall history lookups to supplier recall risk due diligence and procurement decisions.

Supplier searchCompany record APIDue diligence result

ERP / SaaS / product sourcing tools

Integrate recall search into your existing product and stop maintaining your own data layer.

User queryGooFuture APIEmbedded result

Compliance and risk teams

Continuously monitor key companies, brands and products to reduce manual work.

Monitoring listMonitoring APIEmail / Webhook

Data and research firms

Use structured historical data for industry trend, company and product risk research.

Research modelAnalytics APIStructured datasets

More than data supply — trends discovered from the data

The following is based on the current database as of August 2026 , a static statistics snapshot used only to illustrate product capability. It is not a live query.

2026 recall records: 391
Involving China manufacturing: 318
Snapshot date: 2026.08
Data status: Static demo

The recall analytics API supports further analysis

Recall trends across countries of manufacture
Frequent safety hazards
Company recall count
Product category risk
Remedy distribution
Annual change trend

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

GooFuture's core value lies before the data reaches the API: turning notices designed for human reading into a data model that is program-friendly, linkable and maintainable.

Entity

Company entity normalisation

Identifies different names for the same company, reducing double counting and missed matches.

Alias → entity

Model

Relational data modelling

Links recalls, companies, products, UPCs, hazards and remedies.

Records → relationship graph

Structure

Structured fields

Converts raw notice information into a program-friendly data structure.

Text → fields

Update

Continuously updated

Regular sync with the latest public data, cutting your maintenance costs.

Source → sync

Deliver

API-first

No need to download the whole database — query and integrate on demand via API.

Query → JSON

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 you need and your expected call volume.
02
Confirm the plan
Confirm endpoint scope, monitoring conditions, delivery method and enterprise support needs.
03
Start integration
Get your API key and integration materials, then wire the JSON results into your ERP, supply chain system or SaaS product.

cURLResponse

curl "https://api.goofuture.com/v1/company/profile?name=Anker" \
  -H "Authorization: Bearer YOUR_API_KEY"

Static demo · JSON response200 OK

{
  "data": {
    "company": "Anker Innovations",
    "recalls": [],
    "updated_at": null
  }
}

From testing to production

Choose a plan by call volume, monitoring conditions, notification method and enterprise support. Your consultant quotes based on your business needs.

Basic

For API testing and product validation

Contact a consultant

Monthly requests: 100
Core endpoints: Company records / recall search
Rate limits: Basic rate limiting
Monitoring conditions: —

Standard

For individual developers and small teams

Contact a consultant

Monthly requests: 5,000
Core endpoints: All core queries
Monitoring conditions: 10 conditions
Notification method: Email

Recommended plan

Professional

For supply chain teams and SaaS products

Contact a consultant

Monthly requests: 50,000
Concurrency: Higher concurrency
Monitoring conditions: 50 conditions
Data delivery: Webhook / CSV

Enterprise

For platforms, data companies and large enterprises

Contact a consultant

Monthly requests: High-volume usage
Data delivery: Incremental data push
Customisation: Field / dataset
Technical support: Enterprise technical support

The questions worth confirming before integrating a data API

Straight answers on public data, update frequency, UPCs, company normalisation and commercial integration.

CPSC raw data is public — why do I still need this API?

If you only need to read a notice occasionally, the official CPSC website is enough. GooFuture is built for teams that need bulk queries, system integration, company entity normalisation, structured data and continuous updates — turning the public files in the US consumer product recall database into data infrastructure that can feed enterprise business systems.

Where does the data come from?

Base recall data comes from US Consumer Product Safety Commission (CPSC) public data. GooFuture collects, cleans, standardises, links and structures the raw data and provides it through an API.

How often is the data updated?

The system continuously syncs the latest CPSC public data. See the API documentation for exact update times and per-API frequencies.

Can I query by UPC?

Yes. If the recall record includes UPC information, you can match on UPC exactly.

Can I still find a company if its name differs?

We normalise company names into entities. When one company has several name variants, the system identifies and links them to the same company entity wherever possible, improving the accuracy of lookups and statistics.

Can I integrate the data into my own SaaS / ERP product?

Yes. The API can be used in internal systems and integrated into ERP, risk tools, supply chain systems, data platforms and SaaS products; commercial usage is governed by the applicable plan and service agreement.

How do I query US CPSC consumer product recall records?

Call the product recall endpoint with a product keyword, model, UPC, company name, country of manufacture, hazard type or date range to run US consumer product recall queries and get structured JSON results.

How do I screen recall risk before listing a cross-border e-commerce product?

Use candidate products, UPCs and supplier names for cross-border e-commerce recall screening, look up similar products and company recall history, and feed the results into product selection, procurement and supplier due diligence.

You no longer maintain a recall dataset yourself.

From collecting CPSC raw data to cleaning, deduplication, linking and continuous updates — we handle it all. Your systems just call the API.

Enterprise consultant onboarding · REST API · JSON responses

US CPSC Recall Data API

Input name variant 3

Master company entity normalised

Data is scattered

Inconsistent company names

Hard to monitor continuously

Maintenance costs keep piling up

Collect

Clean

Normalize

Entity resolution

Relate

Deliver

Company recall record API

Product recall search API

Recall detail API

CPSC recall monitoring API

Recall analytics API

Cross-border e-commerce

Importers / brand owners

ERP / SaaS / product sourcing tools

Compliance and risk teams

Data and research firms

The recall analytics API supports further analysis

Company entity normalisation

Relational data modelling

Structured fields

Continuously updated

API-first

Contact a consultant

Confirm the plan

Start integration

You no longer maintain a recall dataset yourself.