This frustrated me as well, until I realized that the URI contains the recipie ID. For instance the first hit for “Chicken Parm” conatains a URI of

	"http://www.edamam.com/ontologies/edamam.owl#recipe_ed04ad9d33c494f13f6406d53a6de34e"

The part of the URI after the '#' is the recipe ID and can be used at the GET /api/recipes/v2/{id} endpoint to look up that individual recipe record specifically.