If this collector is causing you a problem, email ops@recallproven.com and we will fix it. Please get in touch before blocking us — we would much rather correct the behaviour than discover it by going dark.
How to identify our requests
recall-api/0.1 (+https://recallproven.com/contact)How it behaves
- One scheduled pass per source per day, staggered between 09:30 and 10:30 UTC so that no two sources are fetched at once. There is no continuous polling and no per-user fan-out.
- At most two concurrent requests across all sources.
- Exponential backoff with jitter on errors, and
Retry-Afteris honoured. - Only officially published APIs and bulk downloads are used — no authenticated areas, no working around rate limits, no browser impersonation.
- Responses are archived before parsing, so a parser bug is fixed from our copy rather than by re-requesting your data.
- No personal data is collected, stored or served.
Sources
| ID | Agency | Area | Cadence | Licence |
|---|---|---|---|---|
eu-safety-gate |
European Commission (Safety Gate) | EU | weekly (published every Friday) | CC0-1.0 |
rappelconso |
DGCCRF (RappelConso) | FR | continuous | etalab-2.0 |
cpsc |
CPSC | US | continuous | US-PD |
nhtsa |
NHTSA | US | daily | US-PD |
openfda-device |
FDA | US | weekly | CC0-1.0 |
openfda-drug |
FDA | US | weekly | CC0-1.0 |
openfda-food |
FDA | US | weekly | CC0-1.0 |
Service status
Per-source ingestion freshness is public, with no key required, on the status page and as JSON at /v1/health. The API specification is at /v1/openapi.json.