Curated Recipes News

These are the news items that I have curated during the monitoring of the API space that have some relevance to the Recipes conversation and I wanted to include in my research. I am using all of these links to better understand how the space is defining not just their APIs, but their schema, and other moving parts of their API operations.

These are curated as part of my daily work to understand what is happening across the space, and I regularly use them to track on what has occurred overtime, and include them in my guides, whitepapers, and other outputs.

Recipes Companies and Organizations

These are the organizations I come across in my research who are doing interesting things in the API space. They could be companies, institutions, government agencies, or any other type of organizational entity. My goal is to aggregate so I can stay in tune with what they are up to and how it impacts the API space.


Free recipe app for home cooks. Create a meal plan, grocery list and more from your favorite recipes. Organize your recipe collection and take it anywhere.

  • /grocerylist/item/{guid} DELETE will delete this item assuming you own it.
  • Add a new recipe
  • Add a new review. Only one review can be provided per {userId, recipeId} pair. Otherwise your review will be updated.
  • Add a Recipe to the grocery list. In the request data, pass in recipeId, scale (scale=1.0 says to keep the recipe the same size as originally posted), markAsPending (true/false) to indicate that the lines in the recipe should be marked
  • Add a single line item to the grocery list
  • Delete a Recipe (you must be authenticated as an owner of the recipe)
  • DELETE a reply to a given review. Authenticated user must be the one who originally posted the reply.
  • Delete a review do a DELETE Http request of /note/{ID}
  • Delete a review by recipeId and reviewId. DEPRECATED. Please see recipe/review/{reviewId} for the preferred method. (We are moving from an integer-based ID system to a GUID-style string-based ID system for reviews and replies.)
  • Delete all the items on a grocery list; faster operation than a sync with deleted items.
  • Departmentalize a list of strings -- used for ad-hoc grocery list item addition
  • Feedback on a Recipe -- for internal BigOven editors
  • Get *my* review for the recipe {recipeId}, where "me" is determined by standard authentication headers
  • Get a given note. Make sure you're passing authentication information in the header for the user who owns the note.
  • Get a given review - DEPRECATED. See recipe/review/{reviewId} for the current usage. Beginning in January 2017, BigOven moded from an integer-based ID system to a GUID-style string-based ID system for reviews and replies. We
  • Get a given review by string-style ID. This will return a payload with FeaturedReply, ReplyCount. Recommended display is to list top-level reviews with one featured reply underneath. Currently, the FeaturedReply is the most
  • Get a list of recipe categories (the ID field can be used for include_cat in search parameters)
  • Get a list of recipes that the authenticated user has most recently viewed
  • Get a paged list of replies for a given review.
  • Get a random, home-page-quality Recipe.
  • Get all the images for a recipe. DEPRECATED. Please use /recipe/{recipeId}/photos.
  • Get all the photos for a recipe
  • Get food glossary article
  • Get food glossary article by term (e.g., asparagus). This editorial is (c) BigOven and MUST carry attribution and a link back to the glossary entry on
  • Get paged list of reviews for a recipe. Each review will have at most one FeaturedReply, as well as a ReplyCount.
  • Get recipes related to the given recipeId
  • Get the list of current, seasonal recipe collections. From here, you can use the /collection/{id} endpoint to retrieve the recipes in those collections.
  • Get the recipe/comment tuples for those recipes with 4 or 5 star ratings
  • Get the user's grocery list. User is determined by Basic Authentication.
  • Gets a list of RecipeScan images for the recipe. There will be at most 3 per recipe.
  • Gets a recipe collection metadata. A recipe collection is a curated set of recipes.
  • Gets a recipe collection. A recipe collection is a curated set of recipes.
  • Given a query, return recipe titles starting with query. Query must be at least 3 chars in length.
  • HTTP POST a new note into the system.
  • HTTP PUT (update) a Recipe note (RecipeNote).
  • HTTP PUT (update) a recipe review. DEPRECATED. Please see recipe/review/{reviewId} PUT for the new endpoint. We are moving to a string-based primary key system, no longer integers, for reviews and replies.
  • POST a reply to a given review. The date will be set by server. Note that replies no longer have star ratings, only top-level reviews do.
  • POST an image as a new RecipeScan request 1) Fetch the filename -- DONE 2) Copy it to the pics/scan folder - ENSURE NO NAMING COLLISIONS -- DONE 3) Create 120 thumbnail size in pics/scan/120 -- D
  • POST: /recipe/{recipeId}/image?lat=42&lng=21&caption=this%20is%20my%20caption Note that caption, lng and lat are all optional, but must go on the request URI as params because this endpoint needs a m
  • recipe/100/notes
  • Return full Recipe detail. Returns 403 if the recipe is owned by someone else.
  • Search for recipes. There are many parameters that you can apply. Starting with the most common, use title_kw to search within a title. Use any_kw to search across the entire recipe. If you'd like to limit by course, set the
  • Synchronize the grocery list. Call this with a POST to /grocerylist/sync
  • Update (PUT) a reply to a given review. Authenticated user must be the original one that posted the reply.
  • Update a given top-level review.
  • Update a grocery item by GUID
  • Update a recipe


The smart cooking sidekick that learns what you like and customizes the experience to your personal tastes, nutritional needs, skill level, and more.


Over 130,000 recipes indexed. Search by ingredients on Come join us and lets get cooking!