Ah I see. Well no you cannot pass the id as a GET parameter, it must be part of the URL, that is RESTful design. The tool you are using limits you tremendously if it does not allow you to set URL path params…but can’t you just do url.replace("{id},recipeId)?
when {id} is not a query string parameter e.g. /information?id=XXXXX. I am first calling SearchRecipes and then selecting one recipe ID to be used in calling GetRecipeInformation. The API connector I am using in my application only allows me to build a query string of key/value pairs vs. replace a value in the URL path structure.
Ah I see. Well no you cannot pass the id as a GET parameter, it must be part of the URL, that is RESTful design. The tool you are using limits you tremendously if it does not allow you to set URL path params…but can’t you just do url.replace("{id},recipeId)?
Please forgive my ignorance, but it is not clear to me how to call
GetRecipeInformation //spoonacular-recipe-food-nutrition-v1.p.mashape.com/recipes/{id}/information
when {id} is not a query string parameter e.g. /information?id=XXXXX. I am first calling SearchRecipes and then selecting one recipe ID to be used in calling GetRecipeInformation. The API connector I am using in my application only allows me to build a query string of key/value pairs vs. replace a value in the URL path structure.
Sorry, I don’t quite understand your question. Why should the recipe id not part of the URL?