I spend a lot of time trying to convert the heckyesmarkdown.com service to an API in mashape. It was time consuming and kept on returning me incomprehensible errors. The documentation is unclear on how the APIs are supposed to be documented.
For a purely REST API, this might work, but for something like free-to-find services for which I need a quick-api solution to use, it just does not work. The API documentation editor (seriously, stop calling it documentation and call it specs instead) needs an advanced mode so I can use it better. Another thing I found missing was user help text on the apis themselves.
This might take off to become something like programmableweb, but developers won't rush to it with open-arms unless (a few) major api providers start using this.
For a purely REST API, this might work, but for something like free-to-find services for which I need a quick-api solution to use, it just does not work. The API documentation editor (seriously, stop calling it documentation and call it specs instead) needs an advanced mode so I can use it better. Another thing I found missing was user help text on the apis themselves.
This might take off to become something like programmableweb, but developers won't rush to it with open-arms unless (a few) major api providers start using this.