Hi! There's a new version available (api2), recommended for all new and future development.
We plan to continue to support the legacy version of the API well into 2017 (and later if you let us know), but we do recommend all developers migrate to the new api2 format as your development cycle allows. We strongly recommend that all new recipe and grocery API developers begin with https://api2.bigoven.com
API OVERVIEW
AUTHENTICATION
API PROTOCOL
API DATA
DATA MANAGEMENT
BRANDING, LEGAL & FINANCIAL
Serialization Formats
The BigOven Recipe API currently supports two serialization formats: XML (Extensible Markup Language), and JSON (JavaScript Object Notation).
Requesting a Serialization Format
The API uses the HTTP "Accept" header of the request in order to determine the serialization format of the returned data.
| Serialization Format | HTTP Accept Header |
| XML | text/xml |
| JSON | application/json |
Example to fetch JSON (jQuery)
Here's a simple recipe fetch using jQuery:
function getRecipeJson() {
var apiKey = "your-api-key-here";
var recipeID = 196149;
var url = "https://api.bigoven.com/recipe/" + recipeID + "?api_key="+apiKey;
$.ajax({
type: "GET",
dataType: 'json',
cache: false,
url: url,
success: function (data) {
alert('success');
//console.log(data);
}
});
}
Likewise, here's a simple recipe search:
function getRecipeJson() {
var apiKey = "your-api-key-here";
var titleKeyword = "lasagna";
var url = "https://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);
}
});
}