Join For Free

An open letter to developers. Pls stop fucking up the APIs ecosystem. Posted 1 year ago

Dear developers (API providers),

pls stop fucking up your public APIs.

Every week there is an API that is changing, being shutted down, or malfuctioning. If this trend will continue, we lose trust in using third party services via APIs and we’ll just go back to the old way and reinvent the wheel, by ourself.

Reliabilty and trust are the most important things for this ecosystem. 

We’re seeing an explosion of public APIs, so the trend is strong, but still fragile. 

"next time someone told me why I keep reinventing the wheel, is because the wheel does not work"

This is what I heard, from a developer few weeks back. And you know what? He’s right.  You can’t launch an API, get people relying on you, and then out of nowhere, you wake up and say:

sorry, we’re going to shut down this. Good luck!


Do you want some recent examples?

Twitter is fucking it up - multiple times.

http://scripting.com/stories/2012/07/07/twitterIsACorporateApi.html

Face.com fucked up

http://news.ycombinator.com/item?id=4211021

Simplegeo fucked up

http://news.ycombinator.com/item?id=3457635

I think we’re at a inflection point. Go big or go home. The future of APIs can be: 

1) Third party APIs are going to be mainstream in the software development and they will become THE way we build software.

or

2) They will be left in the dust, because developers have lost trust.

The desitny is attached to all the API providers. The way they are going to RESPECT and MAINTAIN THEIR PROMISES to their developers is crucial, to define the future of this ecosystem. Do less fanfare when you launch an API and stay heads down and keep that API alive as much as you can. There are people that are investing their love and time on you.

Please stop play around, we trust you, we rely on you. Don’t fuck it up. 

Thanks.

Augusto

CEO of Mashape

@sinzone

 

An open letter to developers. Pls stop fucking up the APIs ecosystem. Posted 1 year ago

Dear developers (API providers),

pls stop fucking up your public APIs.

Every week there is an API that is changing, being shutted down, or malfuctioning. If this trend will continue, we lose trust in using third party services via APIs and we’ll just go back to the old way and reinvent the wheel, by ourself.

Reliabilty and trust are the most important things for this ecosystem. 

We’re seeing an explosion of public APIs, so the trend is strong, but still fragile. 

"next time someone told me why I keep reinventing the wheel, is because the wheel does not work"

This is what I heard, from a developer few weeks back. And you know what? He’s right.  You can’t launch an API, get people relying on you, and then out of nowhere, you wake up and say:

sorry, we’re going to shut down this. Good luck!


Do you want some recent examples?

Twitter is fucking it up - multiple times.

http://scripting.com/stories/2012/07/07/twitterIsACorporateApi.html

Face.com fucked up

http://news.ycombinator.com/item?id=4211021

Simplegeo fucked up

http://news.ycombinator.com/item?id=3457635

I think we’re at a inflection point. Go big or go home. The future of APIs can be: 

1) Third party APIs are going to be mainstream in the software development and they will become THE way we build software.

or

2) They will be left in the dust, because developers have lost trust.

The desitny is attached to all the API providers. The way they are going to RESPECT and MAINTAIN THEIR PROMISES to their developers is crucial, to define the future of this ecosystem. Do less fanfare when you launch an API and stay heads down and keep that API alive as much as you can. There are people that are investing their love and time on you.

Please stop play around, we trust you, we rely on you. Don’t fuck it up. 

Thanks.

Augusto

CEO of Mashape

@sinzone

 

Sentimental API to analyze Chinese Text Posted 1 year ago

The Enlighten API is created by Thinkudo Labs and allows text analytics and other functionality for companies, to create their own social monitoring dashboard. 

The API comes with three different plans:

- $10/month

- $500/month

- $1,000/month

Thinkudo Labs was founded in 2012, from a team of developers coming out from SkyScanner and Hewlett-Packard.

If you want to hack on it, just sign up on Mashape using the coupon “thinkudo”.

Happy coding ;)

Kodak can save itself: launch a Print API Posted 2 years ago

In January, the long time leader in the photo/camera industry filled for the Chapter 11 and is shutting down a lot of divisions to arrive afloat for the bankruptcy. It’s even selling more than 1,100 digital image patents to cover the continuos quarterly loss. The company has around $5.1 billion in asset but $6.8 billion in debt.

Yes, Eastman Kodak the company that has invented among other things, the digital camera and handheld camera, files for bankruptcy, after having innnovated for more than 130 years. Recently, the company has been struggling for years, to adapt to an increasingly digital world; since 2003 it has closed 13 manufacturing plants, 130 processing labs and reduced the workforce by 47,000. In some ways it reminds me Apple in 1996. Apple created the PC market, and Kodak created the camera film back in 1880, they both lost their soul at one point. I hope Kodak can find it again, as Apple did. A Kodak camera was used on the Apollo 11 mission in 1969.

It’s always sad when you see an iconic brand, which somehow I assimilate with my childhood’s memories, going away, forever. I beat, everybody will recoginze this:

Kodak has already done a big pivot to save itself. Instead of designing it’s own cameras, will try to license its own brand to other camera makers, also in the last decate they put a lot of effort in the printing business. As they mentioned in the Chapter 11 petition; since 2003 the company have invested havily in inkjet printers and has been working to transform itself from a business primarly based on film and consumer photography to a smaller business with a digital growth strategy focused on the commmercialization of proprietary digital imaging and printing technologies.

In the near future no one will print photos regurarly, like we did in late ‘90 with every camera roll, our camera roll is now digital, we store the best pictures in the cloud, shared via Dropbox, Box or iCloud and add them to our digital photo frame. Actually it was this transition from film to digital that has led some problems to Kodak back at the beginning of the millenium. BUT… I believe that we’ll still print few amazing pictures that we want to keep forever, and print them in a huge size to attach them on the wall of our bedrooms or living rooms, like a wallpaper. 

They basically need to trasform a camera roll (and all the fuctionalities realted with the priting) into an API. And it’s because of all the know-how they have, IPs, the brand and 10 years of investments in the printing business that they should leverage all this, and become a platform, in the cloud, by launching a set of APIs and beginning with a RESTful Print API.

For example a simple Kodak Print API could have these Endpoints: 

Get Order Quote  

GET https://api.kodak.com/v1/print/orderquote

Parameters

APIkeys

paper

size

color

quantity

pngurl (the URL of the PNG you wish to print)

shippingchoice

fullname

streetaddress

apartment

city

state

postalcode

phone

email (optional)

Results

ProductPrice

ShippingPrice

TotalPrice

Example ”JSON”

{“PhotoPrice”:”15.00”,”ShippingPrice”:”10.00”,”TotalPrice”:”25.00”}


Place Order

POST https://api.kodak.com/v1/print/placeorder

Parameters

apikey

paper

size

color

quantity

pngurl (the URL of the PNG you wish to print)

shippingchoice

fullname

streetaddress

apartment

city

state

postalcode

phone

email (optional)

payment method

cctype

ccnumber

ccpostalcode

ccname

ccexpirationmonth

ccexpirationyear

Results

oderid

Example ”JSON”

{“OrderId”:”15-73925-09613”}

Get Order Status

GET https://api.kodak.com/v1/print/orderstatus/{id}

Parameters

APIkeys

orderid

Results

status

submitted

Example “JSON”

{“Status”:”Printing”,”Submitted”:”2012-02-20T11:30:45”}


They have already created some SDKs for developers. But their are doing it wrong!

Kodak APIs can be a big business since the beginnng. They can integrate their APIs into Facebook, Instagram, dating sites, Twitter, Pinterest, Tumblr, Posterous, Foursquare, Flickr and any web and mobile app that has photos as part of their core. This means, reaching almost the entire Internet population = 2 billion of people.

I think that those people are willing to print at least the 2 best pictures every year and have them shipped at home as a big wallpaper. By providing a frustration-free way to print and ship your best moments, without even leave the site you are in, you’re going to increase the conversion of people that will pay Kodak to have this kind of all-inclusive service. 

Only via APIs you can achieve that kind of integration into third party products and platforms.

Assuming that the avarage price per order is $25 and that out of 2 billion potential customers only 1% are going to effectively buy the service (two times a year); this is what comes out:

Yearly Revenue? $25 “price” x 2 “orders/year” x 20M “1% of 2 billion people” = $1 billion.

The new printing era is via APIs, and Kodak still has a big brand and know-how to leverage worldwide. 

Chatterbox Analytics launches a new API! Posted 2 years ago

Chatterbox Analytics (a spin-out company from Queen Mary, University of London) are pleased to announce the release of the new sentiment detection API for social texts. This API is designed specifically to classify short social messages, such as tweets, into positive or negative categories. The system uses advanced statistical models trained (they have partnered with Intel to use their super computer for model training) on 68 million tweets, meaning the detection can handle slang, common misspellings, emoticons, hashtags, etc.


The API comes in two flavors, a free version and a paid-for version which gives users more flexibility;  the system currently supports English, French, Spanish, Portuguese and Dutch.

All the APIs can be found here and we at Mashape are proud to have such a great techology available for our incredible community.
Have fun!

 

Web API’s World Posted 2 years ago

The API market is taking a big shape Posted 3 years ago

(Mashape CEO’s guest post on SiliconANGLE)

An API is a set of programming instructions and standards for accessing a Web based software application or web tool, it’s stand for Application Programming Interface. Since we founded Mashape, “The first APIs Marketplace”, I thought that could be interesting to share some numbers and major players of this new market.

API is a very old concept; but API in the cloud, accessible everywhere from anyone, the so called Open API is a completely new story. In 2000 the first company that embraced this route was Ebay, pushing out some API to help power sellers, than in 2002 came out Amazon and Salesforce in 2003. However the first strong signal was between 2005 and 2007 when Yahoo, Google, Flickr, Skype, Twitter, AOL, Windows Live and Facebook started to push out their APIs. Since then, the trend is growing fast year over year: it took 8 years to get to 1000 APIs, but 18 months to get to 2000 APIs; 2010 has a 2x increase…continue reading

 

The first API marketplace has launched. Posted 3 years ago

Good Morning folks,
it’s 7:30 am (PST) and is an important day for us - we’ve launched the Mashape v0.2

Mashape is a frictionless online marketplace for developers that want to consume or generate and distribute any kind of service via APIs. We provide “RESTful JSON” APIs and traction to any application or service that runs somewhere on a server - instantly.
A warm thanks to the hundreds of developers that have used our product and have helped us with feedbacks, bugs and headed us to the right direction. In particular a big recognition goes to Tom, Keus, Sandro, Max, Dwipal, Kevin, Frank, Jimmy, Jason, Joe, Chris, Matt, Marc, David, Lane, Hunter, Bill, Zander, Mitch, Jude, Travis, Ted, Seth, Evan, Nate, Ken, Philip, Dave, Ted, and Jon.  

Unknown Facts:
45 days required to clean up the code: from 150,000 to 40,000 LOC
Mark Palladino’s fingers - pushing more than 1K new LOC a day (pure Java)
Mike Zonca’s goatee - it’s as much barbaric/wild as our platform architecture
Augusto Marietti’s thick socks - walking in the office like a ghost, the Pier38 is cold at night!
Data migration to MongoDB (MySQL/Hibernate configuration took 3 months, MongoDB 2 weeks)
Design completely reinvented - The Rattotti&Bonardi crew made the magic here (a sense of clean design is now part of us)
354 coffee cups drank by Mike (to stay awake during these two intense months)
1 pound of pasta every dinner with Mark’s sauce
1 300 sq feet studio on Market St. (we squeezed there in 3 and sometimes more)
bicycles for faster moving around SF (one was stolen)
1 flight to Chicago for the CakePHP meetup
2 days of programming brainstorming around Scala, Grails, Java, Ruby, Struts, Spring, MongoDB and CouchDB
5 whiteboards (used to draw shits a thousand of times)
2 things that we can’t tell you
Ken Thom’s “Panettone”
HAPPY HACKING!
For any feedback, question or insult: knock.knock@mashape.com
Hope you’ll like it…

Your app now has an API, automatically. Posted 3 years ago

Applications created on Mashape can be included into other apps created on the platform (see [Including shapes]), but their components (aka “shapes”) can be also called from the outside using our API infrastructure.

This means that a published application has its own APIs and also the client libraries to call them using different popular technologies. For example, your app can be called from:

  • Web Applications
  • Desktop Applications
  • Native Mobile Applications
  • Wherever it’s required

Your app is programmable inside and outside Mashape from day 1!

You don’t have to care about building the wrappers around the APIs, it’s our job. And also, the Mashape Client libraries allow you to call any app on our platform. One library to rule them all.

To start using it, please go to the API - Getting Started document.