Read one CPSC recall by its number
The same public record get_recall returns. No key, no cookie, and no shop or buyer data. Shares /api/check's limit of 60 checks an hour per visitor. Responses use no-store and allow any origin.
Path Parameters
The recall number, as /api/check gives it.
^[A-Za-z0-9-]{1,16}$1 <= length <= 16Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/recalls/27072"{ "found": true, "recallNumber": "27072", "title": "string", "recallDate": "2019-08-24", "url": "string", "description": "string", "products": [ { "name": "string", "model": "string", "type": "string", "units": "string" } ], "hazards": [ "string" ], "remedies": [ "string" ], "image": { "url": "string", "caption": "string" }}Check a product title or model against CPSC recalls GET
Runs the rules a shop's sales get on the text you send. Our code doesn't store or log it. It travels in the page address, so the web host's request logs may include it. At least one of title and model is needed. Limited to 60 checks an hour per visitor.
Not offered. Every answer comes back on its own POST. GET
The server is stateless and opens no event stream, so a GET is refused with 405.