24 May '12, 6am

Episode 352: Securing an API

There are many approaches to locking down an API. Here I start off with HTTP Basic authentication then move on to generating a unique token which can be passed through a URL parameter or HTTP header.

Full article: http://railscasts.com/episodes/352-securing-an-api

Tweets

ASCIIcast 352 - Securing an API

railscasts.com 04 Jun '12, 8pm

, we showed you how to build a versioned API for a store application. We can interact with this application through JSON i...

A few tips on how to build a well-structured AP...

railstips.org 05 Jun '12, 4pm

A few weeks back, we publicly released the Gauges API . Despite building Gauges from the ground up as an API , it was a lo...

Apple Does It Again, Files Patent For A New Pro...

thedomains.com 24 May '12, 4pm

Elliot on Did Rick Schwartz Just Buy The Next Category Killer Domain For Under $4k? Louise on Did Rick Schwartz Just Buy T...

ASCIIcast 348 - The Rails API Gem

railscasts.com 20 May '12, 9pm

With rich client-side applications becoming more popular a common question is “Should I use Rails if all I need to do is p...

Getting Started with the Mozscape API

seomoz.org 21 May '12, 6pm

I’m pretty new here at SEOmoz, and one of the projects I’m working on is improving the Mozscape API wiki content so it’s e...

Mission Control—The Trajectory Blog: Full featu...

robots.thoughtbot.com 22 May '12, 3pm

From Mission Control , the Trajectory blog: We’ve just published full details on the publicly available Uploads and Commen...

@idiot

name.com 21 May '12, 2am

Welcome to the name.com beta reseller api page. Our API (V2) is now available for general use. The API requires programmin...