Recipe Parser API

API ID 1920

The Recipe Parser API enables users to extract online recipes from any website and convert them into a structured format, such as JSON. With this API, users can easily create their own digital cookbook by parsing recipes from various sources. The API's simple and user-friendly interface makes it an excellent tool for developers and cooking enthusiasts alike.

98% uptime 396 ms avg response

API Documentation

Endpoints

Request

Parse the recipe from the entered URL.

 
Endpoint ID: 1629
GET https://zylalabs.com/api/1920/recipe+parser+api/1629/recipe+parser
INPUT PARAMETERS

Recipe Parser — Endpoint Features

Object Description
source Required URL of the receipt page.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

source
API EXAMPLE RESPONSE
JSON
{"status":201,"recipe":{"recipeDiet":[],"recipeCuisine":["mongolian","chinese"],"recipeCategory":["dinner"],"recipeOccasion":[],"recipeUtensils":["whisk","bowl"],"name":"Super-Simple, Super-Spicy Mongolian Beef","image":["https://www.allrecipes.com/thmb/OPRTlH-cDntVlWw-4ThIZ_vkmTo=/1500x0/filters:no_upscale():max_bytes(150000):strip_icc()/385999-9ee53db2a875481bbf4257a0ff0c2a98.jpg"],"description":"This spicy Mongolian beef is marinated with soy, hoisin, sesame, sugar, garlic, and chili, then quickly stir-fried with green onions for a tasty dish.","cookTime":"10 m","cookTimeOriginalFormat":"PT10M","prepTime":"15 m","prepTimeOriginalFormat":"PT15M","totalTime":"85 m","totalTimeOriginalFormat":"PT85M","recipeYield":"4","recipeIngredients":["0.25 cup soy sauce","1 tablespoon hoisin sauce","1 tablespoon sesame oil","2 teaspoons white sugar","1 tablespoon minced garlic","1 tablespoon red pepper flakes","1 pound beef flank steak, thinly sliced","1 tablespoon peanut oil","2 large green onions, thinly sliced"],"recipeInstructions":[{"type":"text","text":"Whisk together soy sauce, hoisin sauce, sesame oil, sugar, garlic, and red pepper flakes in a large bowl. Toss beef with marinade; cover the bowl and refrigerate for 1 hour to overnight."},{"type":"text","text":"Heat peanut oil in a wok or large, nonstick skillet over high heat. Cook and stir green onions in hot oil for 5 to 10 seconds. Remove beef from marinade and add to green onions in the wok; discard marinade. Cook and stir until beef is no longer pink and begins to brown, about 5 minutes."}],"ratingValue":5,"nutritionCalories":"200 kcal","nutritionFatContent":"12 g","nutritionSaturatedFatContent":"3 g","nutritionUnsaturatedFatContent":"0 g","nutritionCholesterolContent":"25 mg","nutritionSodiumContent":"996 mg","nutritionCarbohydrateContent":"8 g","nutritionFiberContent":"1 g","nutritionSugarContent":"4 g","nutritionProteinContent":"15 g","recipeTags":[{"name":"beef"},{"name":"steak"},{"name":"sesame"},{"name":"garlic"},{"name":"onions"}],"searchTerms":"super simple super spicy mongolian beef spicy marinated soy  hoisin  sesame  sugar  garlic  chili  quickly stir fried green onions tasty dish dinner beef  steak "},"url":"https://www.allrecipes.com/recipe/148831/super-simple-super-spicy-mongolian-beef/"}
Recipe Parser — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/1920/recipe+parser+api/1629/recipe+parser?source=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Recipe Parser API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

About the API:

The Recipe Parser API is a powerful tool that enables users to extract online recipes from any website and convert them into a structured output format, such as JSON. With this API, users can easily create their own digital cookbook by parsing recipes from various sources, including popular recipe websites, food blogs, and cooking forums. The API's simple and user-friendly interface makes it an excellent tool for developers and cooking enthusiasts alike.

One of the key features of the Recipe Parser API is its ability to parse recipes from a wide variety of websites. The API's advanced parsing algorithms can detect and extract recipe data from HTML pages, regardless of the website's structure or formatting. This means that users can quickly and easily parse recipes from virtually any website, without the need for complex data extraction tools or custom scripts.

Once a recipe has been parsed, the API generates a structured output format in JSON, which includes all of the relevant recipe data, such as ingredients, cooking instructions, nutritional information, and more. This structured output format makes it easy for users to manipulate and analyze recipe data, and it can be easily integrated into a wide range of applications and platforms.

Another key benefit of the Recipe Parser API is its ability to handle large volumes of recipe data. With the API's robust processing capabilities, users can easily parse hundreds or even thousands of recipes in a matter of minutes. This makes it an ideal solution for developers and organizations that need to process large amounts of recipe data on a regular basis.

The Recipe Parser API also includes a number of advanced features and customization options, such as the ability to exclude certain ingredients or sections of a recipe, customize the output format, and more. These features make it a flexible and versatile tool that can be tailored to the specific needs of each user or application.

In summary, the Recipe Parser API is a powerful and versatile tool that enables users to parse online recipes from any website and convert them into a structured output format, such as JSON. With its advanced parsing algorithms, robust processing capabilities, and flexible customization options, the API is an ideal solution for developers, cooking enthusiasts, and organizations that need to process large volumes of recipe data.

 

What this API receives and what your API provides (input/output)?

Pass the URL from where you want to scrape and parse the recipe of your choice. 

 

What are the most common uses cases of this API?

  1. Recipe Aggregator Website: A recipe aggregator website can use the Recipe Parser API to extract recipe data from various recipe websites and display it in a structured format on their platform. This can help them to create a comprehensive database of recipes that users can browse and search.

  2. Recipe Management App: A recipe management app can use the Recipe Parser API to allow users to import their favorite recipes from various sources and store them in a centralized location. The app can also provide features such as meal planning, grocery list creation, and recipe sharing.

  3. Nutrition App: A nutrition app can use the Recipe Parser API to extract nutritional information from recipes and calculate the total calories, carbohydrates, protein, and fat content of each recipe. This can help users to track their daily intake of nutrients and plan their meals accordingly.

  4. Meal Delivery Service: A meal delivery service can use the Recipe Parser API to extract recipes from various sources and create a meal plan for their customers. They can also use the API to generate grocery lists for each recipe, making it easier for customers to purchase the necessary ingredients.

  5. Cooking Chatbot: A cooking chatbot can use the Recipe Parser API to provide users with recipes based on their preferences and dietary restrictions. The chatbot can also assist users with cooking instructions, ingredient substitutions, and other cooking-related queries.

 

Are there any limitations to your plans?

Besides API call limitations per month, there are no other limitations. 

Recipe Parser API FAQs

The Recipe Parser API returns structured recipe data in JSON format, including fields such as recipe name, ingredients, cooking instructions, nutritional information, preparation and cooking times, and images.

Key fields in the response include "name" (recipe title), "recipeIngredients" (list of ingredients), "cookTime" (cooking duration), "prepTime" (preparation duration), "recipeCuisine" (cuisine type), and "image" (recipe image URLs).

The response data is organized in a JSON object with a "status" field indicating the request outcome and a "recipe" object containing all relevant recipe details, making it easy to parse and utilize in applications.

The endpoint provides comprehensive recipe information, including ingredients, cooking instructions, dietary categories, cuisine types, preparation and cooking times, and serving sizes, allowing for detailed recipe management.

Users can customize their requests by specifying the URL of the recipe they wish to parse. Advanced features may allow for excluding certain ingredients or sections, though specific customization options should be checked in the API documentation.

The Recipe Parser API extracts data from various online sources, including popular recipe websites, food blogs, and cooking forums, utilizing advanced algorithms to ensure accurate data extraction regardless of website structure.

Data accuracy is maintained through the API's advanced parsing algorithms, which are designed to detect and extract relevant recipe information from diverse HTML structures, ensuring reliable and consistent output.

Typical use cases include creating recipe aggregator websites, developing recipe management apps, building nutrition tracking tools, generating meal plans for delivery services, and powering cooking chatbots for user assistance.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs