Too much load on launch day? I get a "Oops, an error occured :S" screen Edit: back now
[deleted]
The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
11–20 of 29 posts
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#12Craigslist isn't participating? That's surprising!
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#13I 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.
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#14I 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 e…
From the sounds of it the Creators are reaching out to some bigger players in the API game.
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#15Standardizing APIs is a Good Thing. Unfortunately, standards alone don't seem to be enough. (oAuth2 anyone?)
Therefore, offering a proxy that has enough benefits to developers to make them switch to it's standard seems like a more realistic approach.
So, I truly hope Mashape takes off.
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#16I 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 e…
Hi, 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
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.
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#17I don't know how useful the clients in different languages are when all the client code returns is a JSON object.
I would have thought that the whole point of a custom client would be that it would expose objects and methods that had represented the request and response data for the API.
If I have to interpret and parse the JSON myself then the client code they provide isn't very useful IMHO.
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#18I was fortunate enough to spend a couple days with these guys when I was first getting my feet wet a few months back. Although my chops weren't built enough yet for what they needed, I enjoyed doing a little problem solving with them and getting to see my first glimpse of startup life. They were super nice and they really had a passion and dedication for Mashape. It's cool to seen them finally launch.
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#19I found Mashape via google as I was looking for a simple way to monetize our API (and get some exposure) about a year ago. We posted our Whois API (http://www.mashape.com/nametoolkit/name-toolkit) on Mashape.
In the early days it was quiet but I liked the auto-generated clients. It's really been picking up in the last few months and the hassle-free billing, documentation is great. Augusto is great, he is still personally answering mails when there are issues.
What could be improved on: Better stats for the admin interface, .NET support (I'm aware this has been on their roadmap but customers have repeatedly asked me for this), more payout options like bank transfer would be awesome too.
Re: The API Hub: Jeff Bezos-Backed Mashape Launches To The Public With 430 APIs
#20I found Mashape via google as I was looking for a simple way to monetize our API (and get some exposure) about a year ago. We posted our Whois API ( http://www.mashape.com/nametoolkit/name-toolkit ) on Mashape. In the early days it was quiet but I liked the auto-generated clients. It's really been picking up in the last few months and the hassle-free billing, documentation is great. Augusto is great, he is still pers…
Do the auto generated clients only return JSON for each client library? Do you still need to write your own parser to parse the JSON?
* Nevermind. Yes they return JSON, I just read the documentation.