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.
Pass the URL from where you want to scrape and parse the recipe of your choice.
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.
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.
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.
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.
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.
Besides API call limitations per month, there are no other limitations.
Parse the recipe from the entered URL.
Recipe Parser - Endpoint Features
| Object | Description |
|---|---|
source |
[Required] URL of the receipt page. |
Continue with Google
Continue with Github
{"status":201,"recipe":{"error":"We couldnt find any recipe data on that page","message":"We couldnt find any recipe data on that page"},"url":"https://www.ricardocuisine.com/recettes/9931-one-pot-de-couscous-aux-boulettes-de-merguez"}
curl --location --request GET 'https://zylalabs.com/api/1920/recipe+parser+api/1629/recipe+parser?source=https://www.allrecipes.com/recipe/21014/good-old-fashioned-pancakes/' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
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, look at the ‘X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
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 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
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]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
599ms
Service Level:
100%
Response Time:
1,966ms
Service Level:
100%
Response Time:
811ms
Service Level:
97%
Response Time:
558ms
Service Level:
100%
Response Time:
5,089ms
Service Level:
100%
Response Time:
2,162ms
Service Level:
100%
Response Time:
544ms
Service Level:
100%
Response Time:
733ms
Service Level:
100%
Response Time:
684ms
Service Level:
100%
Response Time:
712ms
Service Level:
100%
Response Time:
902ms
Service Level:
91%
Response Time:
604ms
Service Level:
100%
Response Time:
457ms
Service Level:
100%
Response Time:
3,228ms
Service Level:
99%
Response Time:
2,352ms
Service Level:
100%
Response Time:
1,568ms
Service Level:
100%
Response Time:
641ms
