"I’ve been looking for an excuse to try Martini ever since it was announced on the golang-nuts mailing list. Martini is a Go package for web server development that skyrocketed to close to 2000 stars on GitHub in just a few weeks (the first public commit is a month old). So I decided to build an example application that implements a (pragmatic) RESTful API, based on mostly-agreed-upon best practices."
"Quickly create fake APIs for use in client-only tests or prototypes."
"There seems to be a couple of common concerns that people have about introducing hypermedia to their APIs. There’s a thread on the api-craft mailing list called “Selling the benefits of hypermedia” where these were voiced. I’d like to address them here."
"A guide on creating an OAuth server, both OAuth 1 and OAuth 2, in a flavor of Flask with the help of Flask-OAuthlib."
"Let's take a look at how we can alleviate rate-limiting woes by utilizing a background job system. In this example we'll use delayed_job, since it provides the ability to retry failed jobs."
"At POP, our site is entirely API driven. We separated our frontend codebase from our backend API in it’s entirety. The two sites are even in separate repositories. There are several reasons we decided to use this architecture, which I'll cover below."
A guide on how to create an API with Symfony2.
"Today we’re introducing Runscope Radar: automated backend service testing and API monitoring for app developers. With Runscope Radar you can build tests that verify your services are returning expected data and receive notifications when things go wrong."
"When we first started design discussions for version 2.0 of the Znode API, we talked about all kinds of things. What should the URLs look like? What technology should we use to build it? Should we support both JSON and XML or just one or the other? If based on REST, how far do we take it? How do we make the endpoints flexible enough to support robust querying and filtering? We asked ourselves all kinds of questions, and in doing so we came up with a few tenets that guided our approach to the overall design and implementation of the API."
"While OAuth was originally designed to allow service providers to delegate some access on behalf of a customer to a third party, and we do use it that way too, Heroku also uses OAuth for SSO. We'd like to take this opportunity to provide a technical overview."
"Let's learn about some ways HTTP requests can fail and how you can write a production-ready, robust HTTP client to work around these."
"This post will provide one example and explain why you might consider using hypermedia based on this example. The reason for this is that implementing hypermedia systems is a non-trivial activity. It has performance, maintenance, and developer ramifications. This example illustrates a scenario and highlights the benefits of this extra effort."
"Developers and businesses rely on the stability and consistency of the GitHub API for critical tasks. Changes to the API could break production deployments (or continuous integration, authentication, etc.) for thousands of businesses. And yet, GitHub.com continues to evolve, improving existing features, and adding new ones. The GitHub API needs to evolve as well. We'll explore the design philosophies and techniques that we use to provide a reliable API, while continuing to ship improvements every day."
"ASP.NET Web API 2 has been released with a number of new exciting features. In this web development post, I'll try to discuss new features of it which can be considered the top 5."
"In this blog post, I'll walk through creating a sample project that exposes a ReST API consumed by AngularJS on the client to showcase how to combine the frontend and backend frameworks to simplify creating complex applications. I'll make heavy use of code examples to demonstrate both the solution and the process and there's a companion Github project with all the code."
"Build the backlog for your API product based on real experiences. Study the behavior of the developers who want to use your core business value. Your software might provide serious value, but if it’s not easy to get started you might never have a chance to be considered."
"With the emergence and popularity of REST APIs, there is a need to define a layer dedicated to the performing API-related functions. This article tries to define these responsibilities and separate it from the responsibility of other layers."
"In this post I will show you an approach I found helpful to integration testing HTTP APIs built on top of ASP.NET Web API."
"This screencast provides an introduction to the new Grails 2.3 REST support for creating APIs."