Would it be possible to add the ability to parse “to taste”? A majority of our recipe rejections are kicked back on:
“Salt and pepper to taste”
“Pepper to taste”
“Sea salt, to taste”
We’ve been manually changing these to “1/8 tsp pepper” or “1/8 tsp salt” when we see them just to get them to parse through the API. I realize that this is a particularly subjective ingredient to put an amount and value to, but it would be nice if we could somehow automate processing these extremely common ingredient listings.
Our natural API endpoint is set to just disregard unrecognized phrases like “to taste” so that should not be causing an issue on our end.
Can you please try our demo interface and confirm if you can replicate any problem there?
Is this the most current API URL for natural language parsing of ingredients?
Yes, though we recommend pointing to /v2/ in the URL instead of /v1/ the result will be the same regardless of which version number you use.