BigOven API

Name: BigOven API API
Brand: BigOven API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey, basic17 EndpointsREST

For Agents

Search BigOven recipes, fetch a recipe with photos and reviews, and add ingredients from a recipe directly to a user's grocery list.

Quickstart

Get started with BigOven API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"find a recipe"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BigOven API API.

Search the BigOven recipe catalog by keyword, cuisine, or course via /recipes

Retrieve a full recipe with ingredients and directions through /recipe/{recipeId}

Fetch a random recipe with /recipe/random for daily-meal suggestions

Autocomplete recipe titles as a user types via /recipes/autocomplete

GET STARTED

Start building with BigOven API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for BigOven API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for BigOven API, keeping it validated and agent-ready. BigOven is a recipe, meal-planning, and grocery-list service with a catalog of hundreds of thousands of recipes searchable by keyword, ingredient, or random pick. The API exposes recipe lookup, photos, reviews, autocomplete, related-recipe suggestions, and a personal grocery list that can be appended to from a recipe in one call. Authentication uses an X-BigOven-API-Key header for read access and HTTP Basic for user-scoped write operations like grocery list updates and reviews.

Use Cases

Patterns agents use BigOven API API for, with concrete tasks.

★ Recipe Search and Discovery

Cooking apps and meal-planning bots query BigOven's catalog by keyword and dietary filter to surface recipes that match the user's intent. The /recipes endpoint accepts free-text queries and returns paginated results with title, ID, and thumbnail, while /recipes/autocomplete powers a fast type-ahead box. /recipe/random gives a stress-free 'surprise me' option for users who don't know what they want to cook.

Call /recipes with title_kw='chicken curry' and rpp=10, return titles and recipeIds, then call /recipe/{recipeId} for the top match

Grocery List Automation

Meal-prep apps push the ingredients from a chosen recipe straight into the user's BigOven grocery list, then call /grocerylist/departmentalize to bucket them by store aisle. The flow uses /grocerylist/recipe/{recipeId} for one-shot population and /grocerylist/item for ad-hoc additions, with HTTP Basic auth scoping the writes to the signed-in user. This removes the manual transcription step that kills retention in DIY meal-planning workflows.

Call /grocerylist/recipe/{recipeId} for recipe 98765 as the authenticated user, then call /grocerylist/departmentalize and return the grouped aisle list

Related-Recipe Recommendations

Recipe sites and chatbots boost engagement by surfacing related dishes after the user views a recipe — same cuisine, same hero ingredient, or matching course. /recipe/{recipeId}/related returns BigOven's curated similarity list without needing the integrator to build their own embedding store. Combined with /recipe/{recipeId}/photos and /recipe/{recipeId}/reviews, the related list powers a full inline browse experience.

Call /recipe/{recipeId}/related with recipeId=12345, return the top 5 related titles and IDs for an inline 'You might also like' panel

Agent-Driven Meal Planning via Jentic

An AI cooking assistant connected through Jentic answers 'what's for dinner tonight?' by calling /recipe/random, then lists ingredients and asks if it should add them to the grocery list. Jentic holds the BigOven API key and the user's Basic auth credentials separately, so the agent can mix read and write operations without ever touching the secrets. The agent only needs to declare the high-level intent.

Search Jentic for 'find a recipe', load BigOven /recipe/random, execute, then load /grocerylist/recipe/{recipeId} and execute with the returned recipeId

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for bigoven api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/recipes

Search recipes by keyword and filters

GET

/recipe/{recipeId}

Retrieve a full recipe with ingredients and directions

GET

/recipe/random

Fetch a random recipe

GET

/recipes/autocomplete

Autocomplete recipe titles

GET

/recipe/{recipeId}/related

List recipes related to a given recipe

POST

/grocerylist/recipe/{recipeId}

Add a recipe's ingredients to the grocery list

POST

/grocerylist/departmentalize

Group grocery list by store department

GET

/me

Retrieve the authenticated user profile

GET

/recipes

Search recipes by keyword and filters

GET

/recipe/{recipeId}

Retrieve a full recipe with ingredients and directions

GET

/recipe/random

Fetch a random recipe

GET

/recipes/autocomplete

Autocomplete recipe titles

GET

/recipe/{recipeId}/related

List recipes related to a given recipe

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BigOven's X-BigOven-API-Key header value and per-user HTTP Basic credentials are stored encrypted in the Jentic vault. The agent invokes operations by name, and Jentic attaches the right header pair at call time so secrets never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'find a recipe', 'add ingredients to my grocery list') and Jentic returns the matching BigOven operation with its parameter schema, so the agent calls the correct endpoint without parsing the docs.

Time to first call

Direct BigOven integration: 1 day handling dual auth flows, paginated search, and grocery list state. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Spoonacular API

Recipe search plus full nutritional analysis and meal planning

Choose Spoonacular when you need calorie and macro nutrition data alongside recipes; choose BigOven when grocery list integration and a curated catalog matter most

Alternative

Edamam API

Recipe search and food database with diet and allergen filtering

Choose Edamam for strict diet and allergen filtering on recipes; choose BigOven for built-in grocery list endpoints and recipe collections

Complementary

Food Standards Agency API

UK food hygiene rating data for restaurants and food businesses

Pair with BigOven when a UK-focused cooking app also wants to surface food hygiene ratings for nearby restaurants

FAQs

Specific to using BigOven API API through Jentic.

Why is there no official OpenAPI spec for BigOven API?

BigOven does not publish an OpenAPI specification — its REST API is documented in narrative form on api2.bigoven.com. Jentic generates and maintains this spec so that AI agents and developers can call BigOven API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the BigOven API use?

Read endpoints use the X-BigOven-API-Key header. User-scoped write endpoints, like grocery list updates and posting reviews, additionally require HTTP Basic credentials for the BigOven account that owns the data. Jentic stores both the API key and the user credential pair separately in the vault and supplies them per call.

Can I add a whole recipe's ingredients to a grocery list in one call?

Yes. POST /grocerylist/recipe/{recipeId} as the authenticated user appends every ingredient from the specified recipe to the user's BigOven grocery list. Follow up with /grocerylist/departmentalize to bucket the list by store aisle.

What are the rate limits for the BigOven API?

BigOven does not publish rate limits in the spec — practical limits depend on the API key tier issued by BigOven. For high-throughput recipe ingestion, batch search calls server-side and cache /recipe/{recipeId} responses since recipe content changes infrequently.

How do I find a random recipe through Jentic?

Run `pip install jentic`, then `await client.search('find a random recipe')`, `await client.load(...)` for BigOven /recipe/random, and `await client.execute(...)`. Jentic injects the X-BigOven-API-Key header from the vault and returns the parsed recipe JSON.

Does the API return nutritional information?

BigOven recipe responses focus on title, ingredients, directions, photos, reviews, and related recipes. Detailed per-serving nutritional facts are not part of this spec — pair with a nutrition-data API if calorie or macro information is required for the integration.