Recipe Finder API

Access a vast collection of delectable recipes effortlessly with our user-friendly API.

The Recipe Finder API is designed to facilitate quick and accurate access to recipes of all kinds. Its main purpose is to simplify the search for culinary preparations through customized queries, returning complete results that include ingredients, step-by-step instructions, number of servings, and, in many cases, additional notes that enrich the gastronomic experience.

This API is ideal for users looking to integrate smart features into their projects. Whether for mobile recipe apps, virtual cooking assistants, meal planning services, or food blogs, it allows users to enjoy a seamless experience when finding relevant recipes without having to browse multiple sources.

One of the highlights of the Recipe Finder API is its ability to provide rich, detailed results. Each response includes a clear list of ingredients, the quantities needed, and preparation instructions organized in an easy-to-follow format. This ensures that users can successfully reproduce the recipe in their own kitchen, regardless of their level of experience.

In addition to its accuracy, the API provides flexibility in the number of results obtained, making it a tool that can be adapted to different contexts. It can be used to return a single, specific recipe or to generate a varied selection that inspires users to experiment with new preparations.

The speed of response and standardization of information make this API a reliable solution for any technological environment. When integrated, it eliminates the need to manually manage recipe databases, reducing time and effort in the development of food-related projects.

In conclusion, the Recipe Finder API is a comprehensive and versatile solution for those looking to enrich their applications with easy-to-access, clear, and detailed recipes. Its combination of accuracy, speed, and simplicity makes it an essential tool for driving modern, personalized, and engaging culinary experiences.

API Documentation

Endpoints


Search for detailed recipes by query, providing ingredients, instructions, and servings, ideal for culinary applications, meal planning, and food platforms.



                                                                            
GET https://www.zylalabs.com/api/10565/recipe+finder+api/20127/recipe+finder
                                                                            
                                                                        

Recipe Finder - Endpoint Features

Object Description
query [Required] Search query text.
limit Optional Number of results to be returned. Must be between 1 and 30. If not set, the default value of 1 will be used.
offset Optional Number of results to offset for pagination.
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            [{"title": "Low Fat Eggplant Parmesan", "ingredients": "Olive-oil nonstick cooking spray|1 lg Eggplant; (1 1/2 pounds) sliced in 12 rounds|1/2 c Plain bread crumbs|1/4 c Grated Romano cheese|1 Jar low-fat or regular spaghetti sauce|4 oz Part-skim mozzarella cheese (1 cup); shredded", "servings": "4 Servings", "instructions": "1. Heat oven to 425. Lightly coat a cookie sheet with nonstick cooking spray and have ready a 8 or 9 inch square baking dish. 2. Arrange eggplant in a single layer on prepared sheet. Spray eggplant lightly with cooking spray. Bake 15 minutes or until tender and bottoms of slices are golden brown. 3. Reduce oven heat to 375. Mix bread crumbs and Romano cheese in a small bowl. 4. Spread 2/3 cup spaghetti sauce in baking dish. To make stacks: Arrange 4 slices eggplant on sauce. Top eggplant with 2/3 cup sauce. 1/4 cup bread-crumb mixture and 1/3 cup mozzarella cheese.Repeat layers once on top of each stack. Top stacks with the remaining eggplant, sauce and crumb mixture. 5. Bake 15 minutes or until sauce bubbles. Sprinkle with remaining mozzarella cheese and bake 5 minutes longer or until cheese melts. NOTES : 267 calories per serving with 8 grams fat."}]
                                                                                                                                                                                                                    
                                                                                                    

Recipe Finder - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/10565/recipe+finder+api/20127/recipe+finder?query=Eggplant Parmesan' --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 Finder 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.

Simple Transparent Pricing

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

🚀 Enterprise

Starts at
$ 10,000/Year


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

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Recipe Finder API FAQs

The Recipe Finder API returns detailed recipe data, including the title, ingredients, number of servings, and step-by-step instructions for preparation. Each recipe is designed to be clear and easy to follow, catering to users of all cooking skill levels.

The key fields in the response data include "title" (recipe name), "ingredients" (list of ingredients with quantities), "servings" (number of servings), and "instructions" (step-by-step cooking directions). These fields provide comprehensive information for each recipe.

The response data is organized as a JSON array, where each recipe is represented as an object containing key fields like title, ingredients, servings, and instructions. This structure allows for easy parsing and integration into applications.

The Recipe Finder API allows users to customize their search by using parameters such as keywords (e.g., "chicken"), dietary restrictions (e.g., "vegan"), or specific ingredients. This flexibility helps users find recipes that meet their specific needs.

The endpoint provides a variety of information, including recipe titles, ingredient lists, preparation instructions, serving sizes, and additional notes. This comprehensive data helps users understand and recreate recipes effectively.

Data accuracy is maintained through a combination of sourcing recipes from reputable culinary databases and regular updates to ensure that the information remains current and reliable. Quality checks are implemented to verify the correctness of the recipes.

Typical use cases for the Recipe Finder API include mobile recipe applications, virtual cooking assistants, meal planning services, and food blogs. Developers can integrate the API to enhance user experiences with rich recipe content.

Users can effectively utilize the returned data by parsing the JSON response to display recipes in their applications. They can present the title, ingredients, and instructions in a user-friendly format, allowing users to easily follow and replicate the recipes.

General FAQs

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
0ms

Category:


Related APIs


You might also like