Let’s start the news, selfishly, with the ones from Restlet!
- The fun highlight for this week is the D3.js powered interactive HTTP Status Codes Map, that illustrate the HTTP status codes in the form of a subway map, with subway lines for each family of status codes, and when hovering stations, you’ll have a summary and links to the explanations of those codes
- Guillaume Laforge shared the slides and video of his Devoxx conference presentation on the never-ending debate on REST API design
- a screencast by Fabienne Launay on how to improve the performance of your API with some of the APISpark API management features
- how to import CSV files in your API’s data store, when you want to feed your API with existing data or coming from other services
- but you can also export CSV files from your API’s data store, in case you need to do some further data analysis or need to pass that data to a third-party system
- the results of the Summer of APIs virtual hackathon
- a guest blog post at Restlet, by Pierre-Alban Dewitte, showing how to build a multi-player quiz with Socket.IO and APISpark
- Guillaume Blondeau is saving the turtles, with demo built on APISpark, Google Maps, and Angular.JS
- Swann Vichot wraps up the Summer of APIs
APIs are shaping the cities of the future on the APIdays Medium page. To make that happen, the article lists 3 steps to create citizen-focused API automation: offering cadastral & demographic data via APIs, taking a user-centric approach, and applying APIs and data to use case challenges.
Colin Morris lists 3 API trends shaping the future of apps: APIs will drive artificial intelligence, APIs will become software products, and APIs are public service.
SmartBear created an infographic explaining how to calculate the worth of an API.
On API monetization, Jennifer Riggins claims that free APIs can also be profitable.
On The New Stack, Mark Boyd tells about the importance of APIs in the container age.
On Nordic APIs blog, Bill Doerrfeld asks what languages should your API helper libraries support? and how do you connect every company in the world?
Luke Stokes explains why your colleagues still don’t understand Hypermedia APIs.
Neil Mansilla details how to manage API tests with Runscope’s new import/export feature.
An interesting approach of API contract discovery by Stoplight: with a special proxy, by analysing the ongoing traffic, the definition of the API is being discovered. It’s pretty handy to discover the API definition of a big API that has no standard definition (Swagger, RAML, API Blueprint, etc.)
Tapir, a website with a web form to scaffold the structure of your Swagger API definition.
Hugo Wood released version 6.3.0 of Fanfaron, his Java model of the Swagger 2.0 specification, which improves upon swagger-model with a simpler model matching better the Swagger specification.
Darrel Miller puts a fresh coat of REST paint on a SOAP stack.
On the Pusher blog, Phil Leggetter gives 5 reasons why you should have a real-time API.
Andreas Evers presented about Spring REST Docs, a nice approach to documenting RESTful APIs by using your tests, ensuring that your implementation and documentation are always synchronized.
Niklas Heidloff shows the usage of Swagger 2.0 in a Spring Boot application to document APIs.
A Swagger AssertJ test library, from Robert Winkler, which compares a contract-first Swagger with a code-first generated Swagger definition.
A tutorial building an API with Spring REST, OAuth2 and Angular.JS by Eugen Paraschiv.
Abhishek Gupta shows the JSON-P support in JAX-RS 2.
The RAML team comes back on the last two weeks, following the launch of RAML 1.0.
More API news: