Mock sample for your project: 500,000+ Recipe and Grocery List API (v2)

Integrate with "500,000+ Recipe and Grocery List API (v2)" from in no time with Mockoon's ready to use mock sample

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

Version: partner

Use this API in your project

Integrate third-party APIs faster by using "500,000+ Recipe and Grocery List API (v2)" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
It also helps reduce your dependency on third-party APIs: no more accounts to create, API keys to provision, accesses to configure, unplanned downtime, etc.


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 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. 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 apikey right here on this page. Be sure to enter your apikey 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 apikey in with every call, though this can now be done on the header (send a request header "X-BigOven-API-Key" set to your apikey value, e.g., Request["X-BigOven-API-Key"]="your-key-here".)
##Migration Notes
For existing partners, we encourage you to migrate, 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 that we encourage you to read carefully.
See our photos documentation.
For more information on usage of this API, including features, pricing, rate limits, terms and conditions, please visit the BigOven API website.