What's the Difference Between a Recipe and an Open API?

I really think of it as an ingredients versus a recipe. You need to understand what is your API good at and how people are using it. Most organizations believe if they have a developer portal or a relatively simple documentation site that that's sufficient. If you don't have things in a way that people want to consume, they're just not going to adopt it. I personally suffer that frustration because at InGroc we have not released our open API specs yet.