- November 06, 2015

The big news of the week is the launch of the Open API Definition Initiative, hosted by the Linux Foundation, and supported by 3Scale, Apigee, Capital One, Google, IBM, Intuit, Microsoft, PayPal, and Restlet.

Jérôme Louvel of Restlet wrote about Restlet joining the Open API Initiative at the Linux Foundation.

Additional coverage of OAI:

Portside, an investment management company, is using APISpark to shorten time-to-market for its investment research tool.

Jonathan Michaux and Pierre Reliquet developed an API and website on APISpark to discover musical event in their region.

Antoine Richard and Manuel Boilod presented REST from Zero to Hero in 45 minutes at the DevFest conference.

Even non-developers can create an API using popular form services, Zapier, and Restlet, says the API evangelist Kin Lane.

A comparison of microservices frameworks, including Restlet Framework.

Kin Lane blogged about API visualization, showcasing Arnaud Lauret’s experiments with visualizing Swagger API definitions with D3.js.

On Nordic APIs blog, Kristopher Sandoval explains that API keys are different from security, detailing why API keys are not enough. Bill Doerrfeld writes about optimizations of APIs for mobile apps.

Ashley Waxman of Runscope shares 5 steps to monitoring success: by monitoring your APIs frequently, monitoring your key traffic in production, monitoring third-party and partner API, monitoring for API correctness, and getting an overall and complete performance picture.

A tutorial showing how to get nice status pages for your APIs with StatusPage.IO and Runscope.

RAML 1.0 was released, along with a beautiful new website.

MuleSoft, the creators of RAML, also released a beta of their API workbench, an Atom-based IDE for Web API development. Janet Wagner covers it for ProgrammableWeb.

APIDays Paris will look at the impacts of API automation on IT, business and society, and blogged about Human vs APIs: when remote software competes for your job.

API2cart shares some hints & tips for better API error codes, on selecting the appropriate HTTP status code and providing a payload with a readable error message.

Amit Saurav defined a REST API design checklist, talking about versioning, monitoring, retry strategy, layer decoupling, proper dependency management, streamlining payloads, concurrent call handling, caching, security, and user profiling.

Micha Mazaheri compiled a great list of tools that help you develop RESTful APIs, including Paw, HTTPie, and also covers API definitions, hypermedia and monitoring.

An interview of Postman’s CTO on fixing the API workflow

Jennifer Riggins wonders if Hydra can be the universal language for Web APIs and the internet of things.

Another easy tool like Restlet’s APISpark to expose spreadsheets as APIs with APIcastor.

SwaggerGo, a new service to deploy Swagger UI powered API definitions online.

At the SpringOne2GX conference, Jeff Brown presented the RESTful capabilities of the Grails web framework.

Rebecca Franks shows how to mock HTTP responses with Retrofit 2.

Eberhard Wolff contrasts REST vs messaging for microservices in a presentation given at the W-JAX conference.

Ever wondered about the difference between JWT, JWS, and JWE? (JSON Web Tokens, JSON Web Signature, and JSON Web Encryption respectively). Karthik Bhat explains it.

Michael Simons demonstrates documenting APIs with Spring Rest Docs.

Swagger-parser 1.0.12 released, with support for the file:// protocol and support for top-level, shared parameters, responses.

More API news: