Ingredients Parser API

The Ingredients Parser API allows developers to extract ingredient lists from any text. It can quickly and accurately identify and extract ingredient lists from a wide range of sources, including recipes, food labels, and product packaging, and it can return the ingredients in a structured format, making it easy to use in a variety of applications.

About the API:

The Ingredients Parser API is a powerful tool that allows developers to easily extract ingredient lists from any text. Whether you're working on a recipe app, a nutrition tracking platform, or a grocery delivery service, this API can help you quickly and accurately identify and extract ingredient lists from a wide range of sources, including recipes, food labels, and product packaging.

One of the key benefits of this API is its ability to return ingredients in a structured format, making it easy to use in a variety of applications. The API can parse ingredients in multiple languages and can return them in a machine-readable format, allowing developers to easily integrate the data into their own systems.

This API also allows for the identification and extraction of allergens, this feature is particularly useful for food and nutrition-related apps that need to provide allergen information to users. The API can detect allergens based on the ingredient lists, and it can return this information in a structured format, making it easy for developers to integrate allergen information into their apps.

With its ability to extract ingredients from a wide range of sources and its support for multiple languages, the Ingredients Parser API is a powerful tool that can help developers create better food and nutrition-related apps and services. Whether you're working on a recipe app, a nutrition tracking platform, or a grocery delivery service, this API can help you quickly and accurately identify and extract ingredient lists, providing your users with the information they need to make better food choices.

 

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

Pass the ingredients list to the API and receive the ingredients parsed on the response. Simple as that. 

 

What are the most common uses cases of this API?

  1. Recipe websites and apps: The Ingredients Parser API can be integrated into recipe websites and apps to extract ingredient lists from recipe text, making it easy for users to see what ingredients they need to buy before they start cooking.

  2. Nutrition tracking apps: The API can be used to extract ingredient lists from food labels and packaging, allowing users to easily track the nutritional information of the food they eat.

  3. Meal planning apps: The API can be used to extract ingredient lists from recipes and food labels, making it easy for users to plan out their meals for the week and ensure they have all the necessary ingredients on hand.

  4. Allergen detection apps: The API can be used to detect allergens based on ingredient lists, helping people with allergies or food sensitivities make safe food choices.

  5. Grocery delivery apps: The API can be integrated into grocery delivery apps to extract ingredient lists from recipes and food labels, making it easy for users to order the ingredients they need for a specific dish.

  6. Food research and analysis: The API can be used by researchers and food industry professionals to extract and analyze ingredient lists from a wide range of sources, providing valuable insights into food trends and consumer preferences.

 

Are there any limitations to your plans?

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

API Documentation

Endpoints


The Ingredient Parser API extracts and classifies the individual components that comprise an ingredient. The parsing algorithm utilizes C++ machine learning in the back-end to quickly parse and return the provided ingredient string as a structured JSON object.



                                                                            
POST https://zylalabs.com/api/946/ingredients+parser+api/765/parser
                                                                            
                                                                        

Parser - Endpoint Features

Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"ingredients":[{"error_code":null,"input":"3 to 4 tbsp whole milk","quantity":"3","unit":"tablespoon","name":"whole milk","quantity_end":"4","size":null,"suggested_amount":null,"comments":null},{"error_code":null,"input":"8 large Granny Smith apples - peeled, cored and sliced","quantity":"8","unit":null,"name":"Granny Smith apples","quantity_end":null,"size":"large","suggested_amount":null,"comments":"peeled, cored and sliced"},{"error_code":null,"input":"1 can (10-ounce) tomato sauce","quantity":"1","unit":"can","name":"tomato sauce","quantity_end":null,"size":null,"suggested_amount":"10 ounce","comments":null}],"error":{"code":null,"message":null}}
                                                                                                                                                                                                                    
                                                                                                    

Parser - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/946/ingredients+parser+api/765/parser' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
    "ingredients": [
        "3 to 4 tbsp whole milk",
        "8 large Granny Smith apples - peeled, cored and sliced",
        "1 can (10-ounce) tomato sauce"
    ]
}'

    

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 Ingredients Parser API REST 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 commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • 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

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 1000 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 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

Category:


Related APIs