Support

My verification email didn't arrive

It comes from noreply@recalldb.app and usually arrives within a few minutes. Check your spam or junk folder and mark it "not spam". Gmail's Promotions tab and Outlook's Other tab sometimes catch it too.

On the "Email sent" page, press Resend. You can ask 3 times an hour, at least a minute apart. The link works once and expires in 30 minutes. If the address already has a key, we send an email about managing it instead. Still nothing? Write to support@recalldb.app from another address.

I lost my key, or I want a new one

We cannot show a key again, because we keep only a hash of it. Use Manage my key: enter your email, open the one-time link, and choose Rotate my key. You get a new secret at once and the old one stops working. The key id stays the same.

Delete my key and my data

Use Manage my key and choose Delete my key and its data. It removes the key, your usage records, your signup answers and the hash of your email. A key that was suspended or revoked for misuse is kept so the same person cannot start over; see the privacy policy. For access requests or anything else, write to support@recalldb.app.

I hit my rate limit

The free tier is 1,000 requests a month and 10 a minute. A 429 error says which one: rate_limited (wait for Retry-After) or quota_exceeded (the count resets on the 1st, UTC).

Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and GET /v1/usage shows your usage without using any of it. Rate limits in detail. Need more? See pricing and request early access, or write to support@recalldb.app with what you are building.

My key was throttled or suspended

Keys are checked automatically for bulk-copying patterns: record numbers requested in order, machine-speed bursts, a very large number of different records in a day, or several keys used together. A key is first warned, then slowed to 3 requests a minute, then suspended; every step is logged with its reason. To appeal, write to support@recalldb.app with your key id (the 8 characters after "rdb_") and what you are building. See acceptable use.

The data looks wrong

Recall data is copied from NHTSA, CPSC, FDA, USDA FSIS, Health Canada, Transport Canada, CFIA, the UK Food Standards Agency and Product Safety Australia (ACCC) and can be late or incomplete. Check the official notice first: every response has its link in source.official_url. If our copy differs from the agency's, tell us the recall id and what differs at support@recalldb.app; we will correct it or explain. Details: data sources.