Openfoodfacts
/api/v2/product/* endpoint removal
Deprecated, no dateSubscribe to OpenfoodfactsShare
Openfoodfacts has deprecated calls to /api/v2/product/* without a shutdown date. The endpoint remains supported for backward compatibility, but requests will eventually fail once it is removed.
Calls it hits
/api/v2/product/*
What to use instead of these calls
Read products from /api/v3/product/{code} instead. Moving to this endpoint requires updating your response parsing, as the new payload carries status "success", result, errors, and warnings instead of status 1 and status_verbose.
In Openfoodfacts's words
Deprecated — still supported for backward compatibility
Facts
- API
- Openfoodfacts
world.openfoodfacts.org - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Openfoodfacts's own pages
Questions
When does this change take effect?
Openfoodfacts deprecated /api/v2/product/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Openfoodfacts has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.