Published on April 26, 2014
APIs: The good, the bad, the ugly @MicheleTitolo
What we’ll cover
Bonus: it’s interactive
Docs aren’t updated
/users/22445 /products/3156 /movies/127/times
/users/22445 /reviews/3156 /times/127 Not review or time id’s
“Send GET to /remove to delete”
You have all the data you need
Endpoint “id” field /products id /products/:id productID /cart product_id
Yes, this actually happened
We expect certain things
...like image urls having http://
...like dates sent in the same format
We expect certain things to not change
JSON containing HTML
HTTP Basc Auth over SSL
...when SSL is secure
App requests permissions
A single API key
Error message in response
Human readable error message
“There was an error”
Using one of the standards
Manually processing data
• JSONSchema, RAML, API Blueprint, • HTTP 1.1 Spec: http://www.w3.org/Protocols/rfc2616/ rfc2616.html • Charles, Postman • http://runscope.com, also http://newrelic.com for backend analytics • Versioning: http://apiux.com/2013/05/14/api- versioning/ Q&A Resources
Speaker: Matt Stine Developing for the Cloud Track Marc Andressen has famou...
This presentation explains how to develop a Web API in Java using (JAX-RS or Restl...
How to bring innovation to your organization by streamlining the deployment proces...
Cisco Call-control solutions can handle voice, video and data
Nathan Sharp of Siemens Energy recently spoke at the SAP Project Management in Atl...
APIs: the good, the bad, and the ugly. Michele Titolo @micheletitolo; Who's built, designed, and spec'd a lot of APIs; Talk will focus on web APIs, but ...
I've never seen a perfect REST API. But I have seen some of the most horrible mistakes repeated over and over again by people building heavily consumed APIs.
Michele Titolo, iOS app developer and CTO of Women Who Code, gives a New Relic FutureTalk in Portland on the importance of putting user ...
A new blog post by George Reese provides a wealth of recommendations on best practices and common pitfalls of REST APIs implementation.
APIs: the Good, the Bad and the Ugly. Home | Development | APIs: the Good, the Bad and the Ugly
... The Bad, and the Ugly (API Days Paris 2013 ... technology as we know from Kranzberg’s Law is neither good nor bad nor neutral. APIs aren’t ...
Today we feature a deep-dive guest post from Scott Atchley, HPC Systems Engineer in the Technology Integration Group at Oak Ridge National Laboratory.
APIs: The Good, The Bad, The Ugly - Ruby Remote Conf 2015. Published on: 11-03-2015. ... This session will walk through evaluating an API, best practices, ...
... this classic western isn't bad or good or ugly, just moderately interesting. ... API; Licensing; JOIN THE NEWSLETTER. Get the freshest ...