openFDA Device Enforcement Status Watch API

Query the official openFDA device/enforcement endpoint once with an explicit report_date range, report_date descending order and affordable limit of one to twenty records. Keep recall/event identifiers, classification, status, report/initiation/termination date declarations, recalling firm, product description, quantity text and dataset update date. Addresses, personal profiles, code lists, GMDN terms, patient/adverse-event data and contact details are omitted. Product descriptions are literal source text, not parsed device identity or independent classification. A source total greater than returned rows means incomplete coverage; tied dates do not establish a stable page or complete history. No pagination, drug/food query, clinical interpretation, severity scoring, patient-specific recommendation or assertion that a product is safe or that a particular unit is recalled. Data provided by the U.S. Food and Drug Administration. Do not rely on openFDA for medical-care decisions. Source data can be delayed, revised or unvalidated. Anonymous shared-IP access has provider limits; no key or workaround is supplied. Source404 is an error, not a clean zero-recall conclusion.

Input example

{
  "reportDateFrom": "20200101",
  "reportDateTo": "20261014",
  "maxResults": 2
}

Results, snapshots and coverage

Each saved observation is a dataset row with itemKey, contentHash, observedAt and sourceUrl. The hash covers selected semantic fields and excludes volatile retrieval times and request URLs. Copy SNAPSHOT.previousHashes into the next input to compare the same watchlist: NO_BASELINE, FIRST_SEEN, UNCHANGED or CHANGED. There is no automatic durable cross-run memory; only the baseline you provide is compared. Unchanged successful rows are still billed. Missing rows never prove deletions. OUTPUT reports rowsEmitted, actual requestCount, source coverage, errors and completion status. The snapshot complete flag is false when any source fails, a provider stops further requests, or the result/budget cap prevents completion.

Pricing and budget protection

Pay per event: $0.005 startup plus $0.001 per saved observation. Startup quantity follows Apify memory rules (minimum one). Default memory256 MB and timeout120 seconds. No browser, proxy, paid external API, credentials or account-wide permissions. The runtime checks the effective result budget before contacting sources and before saving rows; zero affordable rows causes no source work. Provider list limits are reduced to the remaining affordable capacity. The run has a90-second fetch deadline, two-MiB decoded-body limit, no network retries and no pagination. API rate403/429 or Retry-After stops additional sources. All-source failure exits with an error and a preserved OUTPUT; partial successful observations remain available. Public data or its upstream API may be free: the event fee pays for this bounded workflow, data selection, output validation, snapshots and Apify execution. It does not buy exclusive data or imply endorsement by the provider.

Access and limitations

Only constructed official HTTPS API endpoints are contacted. Arbitrary URLs, private addresses, cross-provider redirects and credential-bearing input are rejected. Provider rate limits and shared-IP quotas apply across runs; do not use parallel runs to defeat a provider limit. For large/bulk extraction use the provider's supported bulk service. This is selected metadata, not independent validation of every source declaration. No guarantee of source availability, completeness, commercial return or suitability for high-stakes decisions is made.

Official source documentation

• https://open.fda.gov/apis/device/enforcement/
• https://open.fda.gov/terms/
• https://open.fda.gov/apis/authentication/