- May 01, 2015

Last week took place the API Strategy & Practice / APIDays Berlin conference. In this new edition of your API weekly news, I’ll start by covering all the great presentations that were given, hence why I’ve called today’s post the Berlin edition!

Mark Boyd covers the beginning of the conference on ProgrammableWeb and 3Scale’s Steven Willmott wraps up the conference.

I’ve collected a few more slide decks of the conference:

Tim Bray’s proposal for a 451 HTTP status code, to signal legal blockage of content, is making progress at the HTTP Working Group of the IETF.

Mashape launches Kong, an Open Source API gateway (coverage on InfoQ and blog post from Nginx which is what Kong is based on).

Auth0 is rethinking backend with web tasks, in the service, for backend-less applications, programmable webhooks, and multitenant sandboxes, as explained by Tomasz Janczuk on his blog and on AWS startup collection’s blog.

Following up Apigee’s ringing the bell of the Nasdaq with its IPO, there’s even a cURL message on the Nasdaq building.

Mike Amundsen is making progress on his Learning Client Hypermedia book for O’Reilly.

On the topic of Hypermedia, Laura Heritage of Akana is wondering if the movement towards hypermedia is really happening. But Jean-Jacques Dubray claims we shouldn’t bother with hypermedia.

Thierry Templier of Restlet demonstrates how to implement OData services with Olingo.

Martin Brennan describes 4 ways APIs can be to gain competitive advantage.

Alan Frye studies the anatomy of an API.

For Nordic API’s blog, Kristopher Sandoval writes about API success and failure, and the importance of API metrics, and Jennifer Riggins describes how APIs are disrupting the way we think.

On SmartBear’s blog, Les Worley explains how to evangelize your API program to internal stakeholders.

Michał Nowak shares his vision of the API landscape in 2015, with Swagger, Hypermedia and Microservices.

Tim Schlechter created an integration to generate Swagger documentation for ElasticSearch clusters to quickly invoke and test the ElasticSearch API.

A handy tool I’ve spotted: the cURL builder, to easily create cURL queries when you don’t remember by heart the parameters for the cURL command-line.

Another one with planb, a kind of proxy tool to serve and refresh some payload, regardless of whether the proxied API is up or down.

Testing REST APIs with the Rest-assured Java library.

Markus Eisele gives a kickstart on API management with JBoss’ Apiman 1.0.

An in other news, the Berlin edition of the essential REST notes, Kin Lane’s weekly API report, and the API developer weekly!

  • QiuYang

    i ask you for help:
    i don’t know how to use role authorization or method authorization. Restlet seem can’t satisfy me. In my client code,how can i get clientresource’s application message? how can i pass the role info into clientinfo. Can challengeAuthdenticator be changed ? how ? Can methodAuthorizer be changed? how? i can’t find a example to explain it.
    please, give me a reply as soon as possable by email.

    • Guillaume Laforge

      I invite you to have a look at the documentation on:

      Those resources should help you get started implementing your use case.