Gets a recipe collection. A recipe collection is a curated set of recipes.

Gets a recipe collection metadata. A recipe collection is a curated set of recipes.

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 user's grocery list. User is determined by Basic Authentication.

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

Add a single line item to the grocery list

/grocerylist/item/{guid} DELETE will delete this item assuming you own it.

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), markAsPe

Synchronize the grocery list. Call this with a POST to /grocerylist/sync

POST: /image/avatar Testing with Postman (validated 11/20/2015): 1) Remove the Content-Type header; add authentication

Given a query, return recipe titles starting with query. Query must be at least 3 chars in length.

Get a list of recipe categories (the ID field can be used for include_cat in search parameters)

Returns stored step number and number of steps in recipe

Stores recipe step number and returns saved step data

Update (PUT) a reply to a given review. Authenticated user must be the original one that posted the reply.

DELETE a reply to a given review. Authenticated user must be the one who originally posted the reply.

Get a given review by string-style ID. This will return a payload with FeaturedReply, ReplyCount. Recommended display is to list top-level reviews

Get a paged list of replies for a given review.

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 NAMIN

Return full Recipe detail with steps. Returns 403 if the recipe is owned by someone else.

Return full Recipe detail. Returns 403 if the recipe is owned by someone else.

Delete a Recipe (you must be authenticated as an owner of the recipe)

Feedback on a Recipe -- for internal BigOven editors

POST: /recipe/{recipeId}/image?lat=42&amp;lng=21&amp;caption=this%20is%20my%20caption Note that caption, lng and lat are all option

Get all the images for a recipe. DEPRECATED. Please use /recipe/{recipeId}/photos.

Get a given note. Make sure you're passing authentication information in the header for the user who owns the note.

HTTP PUT (update) a Recipe note (RecipeNote).

Delete a review do a DELETE Http request of /note/{ID}

Get recipes related to the given recipeId

Get *my* review for the recipe {recipeId}, where "me" is determined by standard authentication headers

Add a new review. Only one review can be provided per {userId, recipeId} pair. Otherwise your review will be updated.

Get a given review - DEPRECATED. See recipe/review/{reviewId} for the current usage. Beginning in January 2017, BigOven moded from an integer-based

HTTP PUT (update) a recipe review. DEPRECATED. Please see recipe/review/{reviewId} PUT for the new endpoint. We are moving to a string-based primar

DEPRECATED! - Deletes a review by recipeId and reviewId. Please use recipe/review/{reviewId} instead.

Get paged list of reviews for a recipe. Each review will have at most one FeaturedReply, as well as a ReplyCount.

Gets a list of RecipeScan images for the recipe. There will be at most 3 per recipe.

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

Get the recipe/comment tuples for those recipes with 4 or 5 star ratings

Get a list of recipes that the authenticated user has most recently viewed

Same as GET recipe but also includes the recipe videos (if any)

1,000,000+ Recipe and Grocery List API (v2)

#Documentation This is the documentation for the partner endpoint of the BigOven Recipe and Grocery List API. The update brings with it Swagger-based documentation. [Swagger](http://swagger.io) is an emerging standard for describing REST-based APIs, and with this Swagger-compliant endpoint (above), you can make ready-to-go interface libraries for your code via [swagger-codegen](https://github.com/swagger-api/swagger-codegen). For instance, it's easy to generate libraries for Node.js, Java, Ruby, ASP.NET MVC, jQuery, php and more! You can also try out the endpoint calls with your own api_key right here on this page. Be sure to enter your api_key above to use the "Try it out!" buttons on this page. ##Start Here Developers new to the BigOven API should start with this version, not with the legacy API. We'll be making improvements to this API over time, and doing only bug fixes on the v1 API. To pretend you're a BigOven user (for instance, to get your recently viewed recipes or your grocery list), you need to pass in Basic Authentication information in the header, just as with the v1 API. We do now require that you make all calls via https. You need to pass your api_key in with every call, though this can now be done on the header (send a request header "X-BigOven-API-Key" set to your api_key value, e.g., Request["X-BigOven-API-Key"]="your-key-here".) ##Migration Notes For existing partners, we encourage you to [migrate](https://api2.bigoven.com), and while at this writing we have no hard-and-fast termination date for the v1 API, we strongly prefer that you migrate by January 1, 2017. While the changes aren't overly complex, there are several breaking changes, including refactoring of recipe search and results and removal of support for XML. This is not a simply plug-and-play replacement to the v1 API. With respect to an exclusive focus on JSON, the world has spoken, and it prefers JSON for REST-based API's. We've taken numerous steps to refactor the API to make it more REST-compliant. Note that this v2 API will be the preferred API from this point onward, so we encourage developers to migrate to this new format. We have put together some [migration notes](/web/documentation/migration-to-v2) that we encourage you to read carefully. ##Photos See our [photos documentation](https://api2.bigoven.com/web/documentation/recipe-images). For more information on usage of this API, including features, pricing, rate limits, terms and conditions, please visit the [BigOven API website](https://api2.bigoven.com).

API	Auth	HTTPS	CORS	Endpoints
1,000,000+ Recipe and Grocery List API (v2)	API key	No	Unknown	66
Open Food Facts	No auth	Yes	Unknown	—
Spoonacular	API key	Yes	Unknown	99
Chomp	API key	Yes	Unknown	4
Edamam nutrition	API key	Yes	Unknown	—
CalorieNinjas	API key	Yes	Yes	1
Jelly Belly Wiki	No auth	Yes	Yes	—
Coffee	No auth	Yes	Unknown	—
Open Brewery DB	No auth	Yes	Yes	—
Edamam recipes	API key	Yes	Unknown	—
TheMealDB	API key	Yes	Yes	—
TheCocktailDB	API key	Yes	Yes	—
BaconMockup	No auth	Yes	Yes	—

Open Food Facts

Spoonacular

Chomp

Edamam nutrition

CalorieNinjas

Jelly Belly Wiki

Coffee

Open Brewery DB

Edamam recipes

TheMealDB

TheCocktailDB

BaconMockup