PUBLIC MARKS with tags api & rest

I’m going to take a little different approach though. I’m not setting out to design the best REST API. My goal is to design the best Tekpub HTTP API. There may be some things borrowed from REST principles, but I’m not interested in designing any API to conform to REST just for REST’s sake. Also, before you get all HATEOAS on me, read the post through then read the section on Hypermedia at the end.

By following the REST style, I would have saved myself either A) having to alter my iOS code and resubmit to the store, or B) time spent researching alternate caching methods and implementing them in Rails. As it stands, my partially-RESTful API is going to cost me (and possibly the client) more time before we can call the project finished.

spire.io provides, as its foundation, a simple REST API. As such, the first thing you do is some discovery to get all the URLs you need to get started.

REST URI relative to

A Web Friendly API?

Pretty REST API docs authored in Markdown

Every time a new Cloud API is announced, its “RESTfulness” is heralded as if it was a MUST HAVE feature. And yet, the most successful of all Cloud APIs, the AWS API set, is not RESTful.

API designers, please note the following rules before calling your creation a REST API

a set of standards that I think should be in place for any REST authentication scheme.

Here's the summary:

1. All REST API calls must take place over HTTPS with a certificate signed by a trusted CA. All clients must validate the certificate before interacting with the server.

2. All REST API calls should occur through dedicated API keys consisting of an identifying component and a shared, private secret. Systems must allow a given customer to have multiple active API keys and de-activate individual keys easily.

3. All REST queries must be authenticated by signing the query parameters sorted in lower-case, alphabetical order using the private credential as the signing token. Signing should occur before URL encoding the query string.

remoteobjects are real subclassable Python objects on which you can build a rich API library. remoteobjects provides easy coding and transfer between Python objects and a JSON REST API. You can define the resources in a RESTful API as `RemoteObject` classes and their properties. These objects then support using the basic HTTP verbs to request and submit data to the API.

API designers, please note the following rules before calling your creation a REST API:

remoteobjects are real subclassable Python objects on which you can build a rich API library. remoteobjects provides easy coding and transfer between Python objects and a JSON REST API. You can define the resources in a RESTful API as RemoteObject classes and their properties. These objects then support using the basic HTTP verbs to request and submit data to the API.