Difference between revisions of "Open Food Facts API Version 2"
Jump to navigation
Jump to search
(Created page with "= Introduction = Version 1 of the Open Food Facts API has been developed organically since 2012, often according to specific needs (in particular the OFF app), and it has bee...") |
|||
| Line 17: | Line 17: | ||
* A direct mapping to the MongoDB format | * A direct mapping to the MongoDB format | ||
* ... | * ... | ||
| + | |||
| + | = APIs = | ||
| + | |||
| + | == Product read API == | ||
| + | |||
| + | == Product write API == | ||
| + | |||
| + | == Images read API == | ||
| + | |||
| + | == Images write API == | ||
| + | |||
| + | == Search API == | ||
| + | |||
| + | * See [[Open Food Facts Search API Version 2]] | ||
Revision as of 10:12, 19 October 2020
Introduction
Version 1 of the Open Food Facts API has been developed organically since 2012, often according to specific needs (in particular the OFF app), and it has been modeled on the structure of the MongoDB database (which itself has evolved organically) and on the Web site (e.g. reusing or mimicking existing CGI forms).
As a result, version 1 of the API is not as standard / simple / easy / powerful / intuitive / documented etc. as it could be.
This page is to discuss the design of a better version 2 of the API.
Desired properties wishlist
What standards should the new API follow, what overally properties should it have etc.?
You can add what you want, and we can discuss it.
- A documentation that matches the implementation
- Non-breaking changes
- A direct mapping to the MongoDB format
- ...