4 ms·
I 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.m
by firlefans 14y ago
I 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 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.
- daveasaurus 14y agoDo 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.
- fosk 14y agoThe client libraries already parse the returned JSON response. Or you can still consume the API without client libraries and get the raw JSON response.
- scottbruin 14y agoNot to rain on your parade, but to anyone looking to try this I just wasted 30 minutes getting setup and trying it to find out that Godaddy, for example, returns next to no results through this service so it's no solution to WHOIS woes.
- firlefans 14y agoFirstly, yes our whois parser needs work, whois is a dirty protocol with lots of inconsistency and we haven't spent enough time dealing with parsing ALL the data out. Oddly enough it has already proved useful to some customers and some fields are consistently parsed well. What's your use case and which fields are you interested in that we failed to parse?