- January 08, 2016

Following up a first part, Thierry Templier continues on his journey to explain what the APISpark platform brings to a Restlet Framework based API.

For InfoQ, Jérôme Louvel interviewed Tony Tam on the OpenAPI initiative and latest Swagger news.

The 2016 API predictions continue, with Steven Willmott highlighting that:

  • security will remain a key issue,
  • automation, microservices and APIs will become a driving force in enterprise IT,
  • engagement and usage information will become even more critical for API owners,
  • bimodal IT will transform into what it needs to be – internal platforms for success for larger companies,
  • Internet of Things applications with APIs will see big visible deployments this year,
  • realtime, evented and hypermedia patterns will become key parts of the API design tool chest,
  • API management will grow in importance for both public and private APIs,
  • citizen integrators and non-technical users will lift the most successful APIs,
  • companies will dig deep into the challenges of identity, security, access control,
  • standards will cause an explosion of tooling,
  • we’ll see at least one pure play API business model company IPO in 2016.

Andy Thurai shares his predictions on IoT, Cloud and APIs, with 2016 being the year of the edge (or how the cloud becomes decentralized), and how machine to machine communication will move to the main stage.

Mark Boyd looking back at 2015, and talking about API deprecation and versioning, saying that they are now a more strategic issue.

Kristopher Sandoval on simultaneous platform-wide versioning: how to implement API to SDK synchronicity.

Sam Macklin: “API security is not an afterthought”, outlining the need for APIs to be secured from the get-go.

Ashley Waxman gives an inside look at 7 standout APIs: Chain, EasyPost, Plaid, Clearbit, Stripe, SendGrid and Clarify, chatting with the men behind those great APIs.

APIs take on increasingly important role as financial technology advances, says Amanda Smith.

Ross Mason on APIs: The invisible warriors in healthcare.

Giovanni Casinelli writes about token design for better API architecture, with advice on the best way to define your API tokens, minimizing the payload, serializing it, encrypting & signing it, and using Base64 to encode it.

Roy Fielding sent a burst of tweets about REST and its tradeoffs that Matthew Reinbold collected.

Jason Harmon gave a presentation on the Do’s and Don’ts of APIs.

Kin Lane announces that the Swagger specification now seems to be named the “OpenAPI spec”. I would have personally loved a fancier name though!

The Swagger project issued a release train with updates to Swagger-JS, Swagger-UI, Swagger-core, Swagger-parser, Swagger-codegen and Swagger-validator!

From the article I mentioned in a previous column from Apiary on the future of API Blueprint, Kin Lane highlights two key aspects of API Blueprint: properly defining body payloads and supporting multiple media types. Two aspects where Swagger seems to be deficient, according to Kin.

James Higginbotham explains how to improve your API conversations with hypermedia, ETags, and realtime APIs, with a nice SMS style chat!

Automating APIs is a good thing, some of the time, says Irakli Nadereishvili.

Siesta: RESTful services made simple in Go by Preetam Jinka.

Phil Sturgeon details approaches for implementing HTTP REST file uploads.

Lorna Jane Mitchell describes how to do API testing with Runscope.

From Monolith to Microservices (part 1): AWS Lambda and API Gateway by Tom Bray.

Data-Oriented Designs for Common API Problems, modeling log in / log out, or password reset, with an API.

APIs and the future of work by Art Anthony.

More API news: