API Design - When to buck the trend (Webcast) from Apigee

API Design - When to buck the trend (Webcast) from Apigee

OAuth and API Providers: Come on Guys!

OAuth and API Providers: Come on Guys!:

If you run a business and decide to become an OAUTH provider or support an API it is essential that you put as much emphasis on this portion of the product as you would on any other core feature.

Web API Design (by apigee)

Web API Design from jyodey

API Design - When to buck the trend (Slides) from Apigee

API Design - When to buck the trend (Webcast) from Apigee

On RESTful API Standards – Just Be Cool: 11 Rules for Practical API Development (part 1 of 2)

On RESTful API Standards – Just Be Cool: 11 Rules for Practical API Development (part 1 of 2):

There are many articles floating around the internet right now about defining RESTful API standards. I’m guessing this is because Ruby on Rails makes it so easy to build an API that everyone and their mom has started building one.

RESTful API Server – Doing it the right way (Part 2)

RESTful API Server – Doing it the right way (Part 2):

In the part 1 of the post, I introduced the RESTful principle and explained how to architecture your server code so as to ensure easier versioning and deprecation of your API. In this part, I’m going to talk briefly about HATEOAS and hypermedia and then show you the role it plays in a native mobile client development. But the crux of this post is going to be centered around how to implement caching (or rather server side support for caching). Target audience include, server developers and to some extent, iOS or any mobile platform developers.

Some Suggestions for Choosing a Token Format for RESTful Web Services

Some Suggestions for Choosing a Token Format for RESTful Web Services:

The most important token format that you need to support for your web apis and RESTful web services these days is: anything. So many platforms define their own authentication/authorization mechanism with what seems to be little concern for standardized formats: API keys here, HMAC signatures there, various OAuth interpretation, etc. Simple does trump standards. For the integration-focused enterprise architect, this reality creates a need for flexible infrastructure supporting arbitrary token formats.