got ya. I checked and while I don’t have a list like the one one stripe, the response for recipe 479101 (new example id) gives you all possible fields.
Thanks for sharing that link. I’m familiar with the endpoint but would like to know all the possible attributes that comprise the recipe object.
If I compare a randomly chosen recipe (#479101) with the example (#156992), I see a number of attributes that don’t exist in the example including:
preparationMinutes
cookingMinutes
dishTypes
… etc.
I’m imagining something akin to how Stripe shares their objects and attributes (https://stripe.com/docs/api#charge_object), or at the least a sample recipe ID that has data for every attribute.
Hi Dave,
got ya. I checked and while I don’t have a list like the one one stripe, the response for recipe 479101 (new example id) gives you all possible fields.
Possible dish types are:
Hope that helps?
Best,
David
Hi David,
Thanks for sharing that link. I’m familiar with the endpoint but would like to know all the possible attributes that comprise the recipe object.
If I compare a randomly chosen recipe (#479101) with the example (#156992), I see a number of attributes that don’t exist in the example including:
… etc.
I’m imagining something akin to how Stripe shares their objects and attributes (https://stripe.com/docs/api#charge_object), or at the least a sample recipe ID that has data for every attribute.
best
dave
Hi, what attributes do you mean?
https://market.mashape.com/spoonacular/recipe-food-nutrition#get-recipe-information gives you a complete response json for a recipe, is that what you are looking for?
Best,
David