1. What's needed as a minimum to get the eaternity data (CO2, water usage, animal welfare, rainforest) in our application? There were some kitchen, product & supply endpoints in the API but I'm not sure if they are mandatory or how they should be used. Can we just post to the Recipe endpoint & get the values to then process in our application?

You would need to query our respective end-points for recipes and supplies. That means: send us information about those parts you want the calculations for.

Indeed, you can just use our recipe endpoint, and process the results in your application. For the usage of our recipe endpoint, you would need to consider the following:

• Amounts for the ingredients need to be send in g/l - we cannot work with „piece“, etc.
• You might want to production / sales quantities with the recipes, because this allows us to also compile a monthly report
• You need to send those recipes towards a "kitchen", which is basically a location.
• You should send us the whole package, that in the end will be displayed to the guests. You can receive for each sub-recipe and ingredient the individual values and evaluation if you send the request while preserving the hierarchies.
• You can provide additional details for every ingredient, as you might already have those fields in your database. In general, I would advice to set everything up, such that if the client starts managing the data it is also sent. We recommend to prepare to send the following additional properties for SKU/food articles, as they are the most important ones for CO2, water, animal welfare and rainforest evaluations.
• Origin (of the food)
• Supplier (name)
• EAN/GTIN numbers
• check: no flight goods
• label: Organic [Which]
• check: TK
• check: Fish from aquaculture (farmed)
• label: Contains certified palm oil or soy [Which].
• label: Animal welfare award [Which]
• label: Other certification [Which]
• In case of convenience products:
• A list of ingredients, in order of decreasing quantity