An API is a machine-to-machine interface which enables our applications to interact with each other. But it is also an interface for the developers that will connect those applications.
That’s a good reason to spend some time working on your documentation.
As a developer, I want the documentation of the APIs I use to be crystal clear, easy to understand and straight-to-the-point. I think that you may have built the better API in the world, if your documentation is poor, unexplicit or hideous (yes, design matters), nobody will ever use it.
Here are some thoughts about how to create a developer-friendly documentation that will boost the interest (and the revenues!) of your API.