We've upgraded BigOven's search to a faster, more powerful platform.

Recipe and Grocery API, Version 2.0

We’ve released a new version of our 350,000+ Recipe and Grocery List Application Programming Interface (API), now available at http://api2.bigoven.com. This API gives developers and data scientists working on applications in the food-tech, health, grocery delivery, home automation field easy, searchable access to recipes at affordable prices.

What’s New

The biggest advancement with the API is that it’s refactored to be much more RESTful. The new Swagger-based endpoint brings with it great productivity improvements for developers.

If you haven’t heard of Swagger, it’s an open API initiative aimed at making powerful, consistent and sharable definitions of RESTful APIs. We’ve provided developers a handy playground to experiment with the BigOven API v2, where you can input parameters in a web form and see actual responses, plus you get code generation tools so you can take the Swagger API definition and build simple “recipe and grocery list building blocks” in your language of choice. So if you’re using Java, Ruby, C#/.NET, jQuery, php, Python, or a popular mobile development framework, you can build your own components that work with the recipe and grocery list API.

Benefits

  • Quickly test out the 350,000+ Recipe and Grocery List API via the Swagger-based developer interface. Very handy during exploration, development and debugging.
  • Get quickly up to speed with Swagger-based documentation. We’re still putting the finishing touches on the documentation, but you’ll find much more extensive descriptions of the endpoints, as well as seeing what each endpoint does.  (Tip: You can put your api_key in the upper right hand corner of the Swagger playground interface and it’ll be remembered between calls.)
  • Use code generation to jumpstart your work in Ruby, Node.js, C#, .NET, Angular.js, jQuery and many more programming languages and frameworks.
  • More REST-ful, newly refactored endpoints for search, recipe display and more
  • Photo redirector – You now can get recipe and user images in a variety of square tile sizes to fit your needs with our photo redirector. These are spread out throughout a Content Delivery Network (CDN), making the experience faster worldwide
  • Recipe categories and subcategories
  • Recipe Collections
  • Support for recipe folders
  • Glossary terms

API2 is being used in production today for our own apps and website, as well as new updates in the works.

Our terms of use and pricing have not changed.

Migration Notes

  • We recommend all new developers start with v2 of the API.
  • We plan to support the older v1 of the API well into 2017, and will monitor usage of that endpoint to determine end-of-life date after January 2017. API v1 is now deprecated but maintained – we will certainly continue to fully support it. We strongly encourage new developers to use API2, and existing API v1 developers migrate to API2 as soon as your development cycle allows, since new features and improvements will be solely on the API2 endpoint.
  • You can use your v1 API key on the new v2 API. Each key will work on both. Starting on a date in 2017 (specific date TBD based on usage and your feedback), API keys will only work on API2.
  • Read other technical migration notes.

BigOven API: Pricing Update for Developers

The BigOven 350,000+ Recipe Application Programming Interface (API) available at http://api.bigoven.com allows any app or web developer to use simple REST-based queries to search over 350,000 recipes and get access to recipe details, ingredients and, depending upon plan, nutrition facts like calorie counts, carbohydrates, protein, display tens of thousands of photos and more.

We’ve seen some great uses of it, from large commercial sites adding a recipe area to their own lifestyle area to fitness studios incorporating healthy recipe suggestions to appliance manufacturers integrating recipe lookup in future consumer electronic devices.

There are no changes for existing paying API partners, but free experimental keys will be phased out on November 1st, 2015.

New Pricing for Entry-level: Plans start at just $99/month

In the two years since it’s been live, we’ve learned a few things. One thing we’ve learned is that while developers always love free — and who doesn’t — it’s most definitely not free to operate and support a free API. Each and every month, we spend thousands of dollars just operating the servers and paying for bandwidth, as well as fielding support requests on usage of the API.

Simply put, we need to better align the cost of operating and expanding the Recipe and Grocery List API with the revenue that supports it. We’ve seen thousands of requests for free experimental keys and while the vast majority of developers have abided by the Terms of Use, we’ve also occasionally seen usage of these free keys well beyond developer-experimental use into commercial usage. That’s regrettable, and one way to ensure only paid plans are used in commercial applications is to only offer paid plans.

So, we’ve made the decision to discontinue the free experimental key level, and are introducing a low-cost $99/month plan.  There is a 30-day money back guarantee on all plans.

These changes will allow us to bring you the support and attention that you need, while still being one of the least-expensive production APIs in the food category, with robust recipe information and search, full JSON and XML support.

What About Existing Free Experimental Keys?

Free keys (starting with “dvx”) will continue to work until November 1st, 2015, but at that time we will phase them out in favor of paid plan keys.  If you already have a paid plan key, you don’t need to do anything.  There are no pricing changes for existing paid keys.

On November 1st 2015, all users of the free experimental keys must transition to a paid plan.  To get an API key, simply visit http://api.bigoven.com.  We’d love to see what you create!

Sample Code: Hello Recipe World

Here’s a simple recipe fetch using jQuery:

<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
<script>
    function getRecipeJson() {
        var apiKey = "your-api-key-here";
        var recipeId = 196149; // simply pass in as shown below
        var url = "http://api.bigoven.com/recipe/196149?api_key=" + apiKey;
        $.ajax({
            type: "GET",
            dataType: 'json',
            cache: false,
            url: url,
            success: function (data) {
                //console.log(data);
                $("#recipeTitle").html(data.Title);
                $("#instructions").html(data.Instructions);
            }
        });
    }
    getRecipeJson();
</script>

Likewise, here’s a simple recipe search:

<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
<script>
        function getRecipeJson() {
            var apiKey = "your-api-key-here";
            var titleKeyword = "lasagna";
            var url = "http://api.bigoven.com/recipes?pg=1&rpp=25&title_kw="
                  + titleKeyword 
                  + "&api_key="+apiKey;
            $.ajax({
                    type: "GET",
                    dataType: 'json',
                    cache: false,
                    url: url,
                    success: function (data) {
                    alert('success');
                    //console.log(data);
                    }
                });
        }
</script>