3 ms·
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 er
by captn3m0 14y ago
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.
- rigelstpierre 14y agoFrom the sounds of it the Creators are reaching out to some bigger players in the API game.
- fosk 14y agoHi, CTO of Mashape here. I'm sorry to hear you had a bad experience when writing the docs, we'll definitely improve the workflow and make it easier to understand. In the meanwhile, I documented your API with my account, and I would be happy to transfer it to yours if you like. Here it is: http://www.mashape.com/thefosk/heck-yes-markdown http://www.mashape.com/thefosk/heck-yes-markdown The documentation it is really a documentation, not all the fields are mandatory by the system, except the endpoint URL, and the parameter's name (we need them to auto-generate the client libraries). All the other fields are optional and provided just for the sake of understandability when a third party needs to consume your API.