- December 18, 2015

The world is abuzz with Star Wars, the force awakens! I had the chance to interview Paul Hallett about the Star Wars API! And don’t worry, if you haven’t seen the movie yet, there’s no spoilers in there!

Lorinda Brandon launches the API Craft blog, a place to explore, question and hypothesize with the API community. I was lucky to be the first one to inaugurate this new API forum with a post on brainstorming a new name for Swagger (also cross posted on the Restlet blog: “a name to walk with a swagger”).

Thierry Templier explains in details what CORS is all about, in this article on understanding and using CORS.

In 2016, the need for an API meta-language will crystallize, says Yves de Montcheuil on InfoWorld, mentioning the various proponents with Swagger, RAML and API Blueprint, and outlining the Open API Initiative. Also, he explains that the Internet of Things will be the main driver for API infrastructure growth.

Arnaud Lauret published a blog post about his presentation from APIdays, on the Star Wars inspired theme of Document-API-topia. The article also provides the slides, as well as the video I recorded of the talk.

Lexy Mayko of API2cart interviews Owen Rubel, covering his memories when at Amazon in the early days, talking about his work on the concepts of API chaining and IO state, his involvement with the Groovy and Grails ecosystem with regards to REST, and more.

Joost Cassee presented about Hypermedia and HAL, explaining how to model business logic as state manipulation, using links and profiles to create a loosely coupled web of API resources, keeping an API malleable while maintaining backward compatibility.

Jason Harmon talked about API design-first in practice, mentioning collaborative contract design, spec-driven development, governance, creating & sharing API standards to follow, discovery through portals, mocks, providing a feedback loop, validating the design, testing and monitoring.

The (Fahrenheit) 451 HTTP status code, pushed by Tim Bray, might actually become an official one, says Mark Notthingham: a status code labeled “Unavailable for legal reasons”, to state that the content is not available as it might have been censored by a government, thus going beyond than a generic 403 which only says that the access to that resource is forbidden.

Zdenek Nemec of Apiary writes about the future of API Blueprint, outlining the MSON syntax, the goals of API Blueprint, the core values, and the roadmap.

An overview of the RAML 1.0 release, and what are the interesting changes in this new version, by Rafal Gancarz of OpenCredo, about the native data types, the enhanced examples, annotations, libraries, overlays & extensions, and tooling.

Lean and mean Open Data machines by Bill Doerrfeld on Nordic APIs blog.

Why is the API economy exploding by Tom Taulli.

What successful API strategies have in common by Mark Boyd.

Oleg Dulin discusses 3 sets of APIs your SaaS platform needs: security, data storage, and metrics.

Craig Williams asks whether REST is best in a micro-services architecture.

Learn about the different JWT signing algorithms, by Sebastián Peyrott, on the Auth0 blog.

Generating API Blueprint docs from your Go API with test2doc.

Building a REST API with Bottle framework, in Python, by Leandro Lima.

Building secure APIs with Express.js and Stormpath, by Randall Degges.

Postman introduces Postman for Mac.

More API news: 

  • API developer weekly #91