openFDA Food Adverse Events (CAERS) — Food and Supplement Reactions

Query the FDA's CAERS database and get flat rows — report number, dates, reported reactions and outcomes, the product and industry, and consumer details.

What you get

reportNumber, dateCreated, dateStarted, outcomes, reactions, industry, productBrand, productRole, consumerAge, consumerGender, consumerCountry.

Sample output

{ "reportNumber": "123456", "reactions": ["NAUSEA", "HEADACHE"],
  "industry": "Vitamins", "productBrand": "ACME VIT", "consumerAge": "45" }

Limitations

• Voluntary, self-reported, and not proof of causation. A reaction listed here is what someone reported, not what a clinician attributed.
• Only the first product on each report is mapped.
• age and gender are often blank; they are returned as null.
• openFDA rate-limits; large sweeps are paced.

Inputs

Input	Type	Default	What it does
search	string	—	openFDA search syntax, e.g

Stops after 1000 rows or 5 requests, whichever comes first — raise maxItems and maxPages for more. Requests are paced 200 ms apart, and pages are fetched by offset (100 at a time).

The dataset's SUMMARY records truncated and stopReason, so a run that hit a cap says so rather than looking like a source that had nothing more.

Pricing

Pay per result.

Fields

Field	Type	What it holds
dateCreated	string	When the record was first created at the source.
dateStarted	string	Date the reported problem or illness began, as reported.
outcomes	string	Outcomes recorded for this report, as the source's own category labels.
reactions	string	Reaction count on the item, as the source records it.
industry	string	Industry classification as the source publishes it.
productBrand	string	Brand name of the food or supplement product.
productRole	string	Role the product played in the report, e.g. suspect or concomitant. The source's own category, and it is an allegation not a finding.
consumerAge	string	Age of the consumer as reported. Often a STRING with a unit.
consumerGender	string	Gender of the consumer as reported.
consumerCountry	string	Country the consumer was in, as a code.

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• openFDA Food Adverse Events — Food and Supplement Reactions declares all 10 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of openFDA Food Adverse Events include dateCreated, dateStarted, outcomes, reactions, industry and productBrand.
• openFDA Food Adverse Events needs no API key, login or account of any kind before its first run.
• Every one of openFDA Food Adverse Events's 3 inputs is optional, so it runs with no configuration at all.
• openFDA Food Adverse Events documents dateCreated as: When the record was first created at the source.
• Every number published about openFDA Food Adverse Events is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• openFDA Food Adverse Events is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

FAQ

What does openFDA Food Adverse Events return?

It returns 10 documented output fields — dateCreated, dateStarted, outcomes, reactions, industry, productBrand, productRole and consumerAge — each with a declared type and a written description. The full schema is below.

What does openFDA Food Adverse Events require to run?

Nothing. All 3 inputs are optional and ship with working defaults.

Does openFDA Food Adverse Events need an API key?

No. It reads only public data and asks for no account.

How is openFDA Food Adverse Events billed?

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.