Recipe API — 1M+ Recipes,
Nutrition Data & Grocery Checkout
Search Pepesto's database of 1 million+ licensed recipes, parse any recipe from a URL, text, or image, and connect the result directly to real supermarket checkout — all in one API.
What is the Pepesto Recipe API?
The Pepesto Recipe API gives developers structured access to a continuously growing database of 1 million+ licensed recipes. It does four things no other single API does together:
Query by cuisine, dietary tag, ingredient, cooking time, or natural-language text. Every result includes full structured data.
Send a URL, free text, or image. The /parse endpoint returns structured ingredients, instructions, and nutrition in one call.
Every recipe includes calories, macronutrients, micronutrients, dietary tags, yield, active time, and per-serving breakdowns.
Map any recipe's ingredients to real supermarket products across 10+ European countries and create a live checkout session in minutes.
The problem with existing recipe APIs
Every developer who has tried to build a food or nutrition product has hit the same walls.
Most recipe APIs are built around USDA data and US grocery chains. European developers building for Tesco, Migros, Albert Heijn, or REWE are left without a path.
Most APIs return stored recipes from their own database only. None reliably parse an arbitrary recipe URL, Instagram post, or image into structured JSON with nutrition data.
Recipe APIs give you data. Shopping is left entirely to you — meaning another vendor, another integration, and months of engineering work to connect ingredients to an actual cart.
See the API in action
Search 1M+ recipes or parse any recipe URL with a single curl call. Every response includes
structured ingredients, nutrition data, and a kg_token you can pass to
/products to build a real supermarket cart.
curl -X POST https://s.pepesto.com/api/suggest \
-H "Authorization: Bearer $PEPESTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "quick vegan pasta for weeknight", "dietary_tags": ["vegan"], "max_time_minutes": 30}'curl -X POST https://s.pepesto.com/api/parse \
-H "Authorization: Bearer $PEPESTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"recipe_url": "https://www.bbcgoodfood.com/recipes/pizza-margherita-4-easy-steps"}'What you can build
The Pepesto recipe API is the data layer for any food product that needs to go beyond just showing recipes.
Search recipes by diet, season, and preference. Serve personalised weekly menus with nutritional summaries. Let users tap "shop this week" and land in a real supermarket cart.
Give your AI agent the ability to suggest meals and place grocery orders. Call /suggest for recipes, /products for matched items, and /oneshot to create the checkout in one step.
Power food logging, calorie tracking, and dietary analysis with structured nutrition data returned by every parse and search endpoint — no manual data entry required.
Ingest third-party recipe URLs and normalise them into your own data model. Add shoppable grocery buttons to any recipe without building a supermarket integration yourself.
Increase basket size by suggesting meal plans to your users. Use the /catalog endpoint to track real-time supermarket prices across European retailers.
Use the /catalog endpoint to monitor and compare product prices across 20+ supermarkets in 13 countries. Receive live updates via webhook when catalogs are re-indexed.
Pepesto vs. other recipe APIs
A fair comparison of the most widely used recipe APIs. Pepesto is purpose-built for the full meal-to-cart journey in European markets.
| Feature | Pepesto | Spoonacular | Edamam |
|---|---|---|---|
| Recipe database size | 1M+ licensed | ~365k | ~2.3M (attributed) |
| Recipe search / query | ✓ | ✓ | ✓ |
| Parse arbitrary recipe URL | ✓ | ~ limited | ✗ |
| Parse recipe from image | ✓ | ✗ | ✗ |
| Nutrition data | ✓ | ✓ | ✓ (separate API) |
| Dietary filters | ✓ | ✓ | ✓ |
| European grocery checkout for recipes | ✓ 13 countries | ✗ | ✗ |
| Catalog / price tracking API | ✓ + webhooks | ✗ | ✗ |
| Revenue sharing for apps | ✓ | ✗ | ✗ |
Competitor data based on publicly available documentation as of early 2026. ✓ = fully supported, ~ = partial/limited, ✗ = not supported.
Permanently licensed recipe database
Pepesto offers permanent, royalty-free licenses to recipes from our curated database. Unlike most APIs where you can only display data temporarily, permanently licensed recipes are yours to store, display, and build on indefinitely.
Full recipe title, detailed cooking instructions, complete ingredient lists with quantities, nutritional information per serving, and an AI-generated hero image.
Permanently licensed recipes go through an extra round of curation and are typically higher quality than results returned by the live /suggest endpoint. Suitable for production content.
Request recipes by cuisine (Italian, Japanese, Mediterranean, etc.), dietary style (keto, vegan, gluten-free), or custom criteria. We'll curate a collection for your specific use case.
See the pricing page for the permanent license cost.
European grocery checkout, out of the box
Every recipe you retrieve via the Pepesto API can be turned into a live supermarket cart across 20+ retailers in 13 European countries — no scraping, no separate contracts, no infrastructure work.
More supermarkets and countries are added continuously. Contact us if you need a specific retailer onboarded for your use case. Full list with domains in the API docs.
Built for developers
Get from zero to a working integration in minutes, not days.
Buy credits via Stripe, call /link with your email, and your API key is returned immediately. Start making real API calls within 5 minutes.
Every endpoint ships with a complete Go protocol definition you can inspect directly in the docs. The response shape is explicit and machine-readable.
Subscribe to supermarket catalog re-indexing via webhook_url on the /catalog endpoint. Receive incremental updates instead of polling.
Apps that pass grocery orders through Pepesto can earn referral revenue. Charge your users a markup on checkout sessions and receive it back as API credits after platform fees.
Purchase credits via Stripe, then call /link with your email — your key is returned immediately. No approval process, no waiting.
Frequently asked questions
Pepesto's recipe database contains 1 million+ licensed recipes spanning hundreds of cuisines,
dietary categories, and cooking styles. The database is continuously growing and is accessible via the
/suggest endpoint.
Yes. Every recipe returned by the Pepesto API includes full nutritional information — calories, macronutrients
(protein, fat, carbohydrates), micronutrients, and per-serving breakdowns. Nutrition data is also returned
when you parse an arbitrary third-party recipe URL via the /parse endpoint.
Yes. The /parse endpoint accepts a publicly accessible recipe URL, free-form text, or an image
and returns structured recipe data including title, ingredients, step-by-step instructions, and nutrition information.
The /suggest endpoint accepts dietary tags and preferences including vegan, vegetarian,
gluten-free, and other dietary constraints. You can also specify cuisine type, ingredients to include
or exclude, cooking time constraints, and the number of servings per result.
See the pricing page for current rates across all endpoints and tiers.
Yes. Pepesto offers permanently licensed recipes with volume discounts available for larger purchases. Permanently licensed recipes include the full title, cooking instructions, ingredient lists, nutritional information, and AI-generated images. See the pricing for current rates or contact us to discuss your domain or volume requirements.
Pepesto does something fairly unique in the space: connects recipes directly to real European supermarket checkout flows, and supports recipe input from any URL, free-form text, or image — including social media recipes.
Pepesto supports grocery checkout at 20+ supermarkets across 10+ European countries: UK (Tesco, Sainsbury's, Waitrose, Asda, Morrisons), Switzerland (Migros, Coop, Aldi Now, Farmy), Germany (REWE), Netherlands (Albert Heijn, Jumbo, Plus), Belgium (Colruyt, Delhaize), Ireland (Tesco IE, Dunnes, SuperValu), Spain (Carrefour), Italy (Esselunga, Conad), Poland (Frisco, Auchan), and Bulgaria (eBag, Bulmag).
Yes. The /parse endpoint supports non-English locales — pass a locale parameter
and the structured recipe data is returned in that language. The /suggest endpoint accepts natural-language queries in any language.