The Recipe Insights Extractor API is designed to transform recipe URLs into comprehensive, structured data. It identifies and organizes critical information such as recipe names, cooking descriptions, ingredient lists, preparation steps, cooking times, yield, and associated imagery. Developers working on food-related applications, blogs, or databases can leverage this API to automate data collection and enrich user experiences. With its easy-to-implement design, the API ensures accurate and consistent data extraction, enabling seamless integration with culinary tools, recipe libraries, and analytics platforms.
Send a recipe URL in the POST body to the endpoint to receive structured data, including ingredients, instructions and more.
extract Recipe Insights - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"name":"Food Safari hummus","description":"A classic dip that is made almost every day in most Lebanese homes. The secret is to cook the chickpeas until they’re really soft. If you can, seek out the prized nine-millimetre chickpeas grown in the Ord River region of Western Australia – they’re fabulous.","images":["https://images.sbs.com.au/dims4/default/9c5d269/2147483647/strip/true/crop/2000x1125+0+0/resize/1280x720!/quality/90/?url=http%3A%2F%2Fsbs-au-brightspot.s3.amazonaws.com%2Fdrupal%2Ffood%2Fpublic%2Fimg_0789_hommus-babaganoush_0.jpg"],"ingredients":["500 g dried chickpeas","2 tbsp bicarbonate of soda","1½ tbsp tahini","1 tbsp lemon juice","1–2 garlic cloves","2 tsp salt","1 tbsp extra-virgin olive oil","1 tsp sweet paprika","finely chopped flat-leaf parsley"],"instructions":[{"steps":["The day before you wish to make the hoummus, place the chickpeas in a large saucepan and add enough cold water to cover by 10 cm or more. Add the bicarbonate of soda and leave to soak overnight.","The next day, rinse the chickpeas, return them to the saucepan and cover with more water. Bring to the boil then simmer for approximately 1–2 hours, until the chickpeas are soft and shedding their skins. Drain and allow to cool.","Place the chickpeas in a food processor and blend until soft and creamy. Add the tahini, lemon juice, garlic and salt and blend again until the mixture is smooth. Scoop into a serving bowl and make a well in the centre. Pour the oil into the well and sprinkle paprika and parsley on top."]}],"url":"https://www.sbs.com.au/food/recipe/food-safari-hummus/73a5wo1e5"}
curl --location --request POST 'https://zylalabs.com/api/5868/recipe+insights+extractor+api/7704/extract+recipe+insights' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"url": "https://www.sbs.com.au/food/recipes/food-safari-hummus"
}'
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.
The Recipe Insights Extractor API can extract detailed information including recipe names, cooking descriptions, ingredient lists, preparation steps, cooking times, yield, and associated imagery.
Developers can easily integrate the Recipe Insights Extractor API by utilizing its straightforward design, which allows for seamless data extraction and incorporation into food-related applications, blogs, or databases.
The API documentation provides specific guidelines on rate limits and batch processing capabilities, which may vary based on the subscription plan or usage tier.
Yes, the Recipe Insights Extractor API is designed to work with a wide range of culinary websites, ensuring accurate extraction of recipe data from diverse sources.
Potential use cases include automating data collection for recipe libraries, enhancing user experiences in culinary applications, and providing analytics for food-related projects.
The API returns structured data including recipe names, descriptions, ingredient lists, preparation steps, cooking times, yield, and associated images, providing a comprehensive overview of the recipe.
Key fields in the response include "name" (recipe title), "description" (cooking overview), "ingredients" (list of items), "instructions" (preparation steps), "images" (visuals), and "cooking time" (duration).
The response data is organized in a JSON format, with each key representing a specific aspect of the recipe, such as "ingredients" as an array and "instructions" as an array of steps, making it easy to parse and utilize.
The endpoint provides detailed information about recipes, including ingredients, preparation steps, cooking times, yield, and images, allowing users to access a full culinary profile from a single URL.
Users can customize their requests by sending specific recipe URLs in the POST body, allowing the API to extract tailored data based on the content of the provided URL.
The data is extracted from publicly available recipe URLs across various culinary websites, ensuring a diverse range of recipes and cooking styles are covered.
Data accuracy is maintained through robust parsing algorithms that validate and structure the extracted information, ensuring that the returned data reflects the original recipe content accurately.
Typical use cases include building recipe databases, enhancing culinary applications with detailed insights, and creating content for food blogs, allowing users to discover and utilize recipes effectively.
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.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
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 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
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.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
3,497ms
Service Level:
100%
Response Time:
7,511ms
Service Level:
100%
Response Time:
261ms
Service Level:
100%
Response Time:
599ms
Service Level:
100%
Response Time:
954ms
Service Level:
100%
Response Time:
5,748ms
Service Level:
100%
Response Time:
471ms
Service Level:
100%
Response Time:
5,687ms
Service Level:
100%
Response Time:
285ms
Service Level:
100%
Response Time:
758ms
Service Level:
100%
Response Time:
6,674ms
Service Level:
100%
Response Time:
7,754ms
Service Level:
100%
Response Time:
3,873ms
Service Level:
100%
Response Time:
5,655ms
Service Level:
100%
Response Time:
2,801ms
Service Level:
100%
Response Time:
5,383ms
Service Level:
100%
Response Time:
7,185ms
Service Level:
100%
Response Time:
464ms
Service Level:
100%
Response Time:
8,259ms
Service Level:
100%
Response Time:
1,190ms