I'm going to be deprecating the current Readernaut API in favor of a newer more built-out version. People using the current version have two weeks to switch over to the new API. Currently you can find your API_KEY by viewing source on any page and searching for "api_key" in the output (this will get better later). Here are some example endpoints:
- Old:
/services/api/USERNAME/notes/
- New:
/api/v1/notes/note/?username=YOUR_USERNAME&api_key=YOUR_API_KEY&user__username=USERNAME
- Old:
/services/api/nathan/readerbooks/
- New:
/api/v1/readerbooks/readerbook/?username=YOUR_USERNAME&api_key=YOUR_API_KEY&user__username=USERNAME
- Old:
/services/api/nathan/goals/
- New:
/api/v1/goals/goal/?username=YOUR_USERNAME&api_key=YOUR_API_KEY&user__username=USERNAME
- Old:
/services/api/nathan/progress/
- New:
/api/v1/goals/progress/?username=YOUR_USERNAME&api_key=YOUR_API_KEY&user__username=USERNAME
This new API is built with Tastypie, if you're interested in what you can do with it you can read over Daniel's documentation.
Why tastiepy > piston? https://bitbucket.org/jespern/django-piston/wiki/Home
Just curious.