Google Reader API Documentation. (99+) Friends of the Unofficial Google Reader API. Using OAuth 2.0 to Access Google APIs - Google Accounts Authentication and Authorization. Basic steps All applications follow a basic pattern when accessing a Google API using OAuth 2.0. At a high level, you follow four steps: 1. Obtain OAuth 2.0 credentials from the Google Developers Console. Visit the Google Developers Console to obtain OAuth 2.0 credentials such as a client ID and client secret that are known to both Google and your application. The set of values varies based on what type of application you are building. 2. Before your application can access private data using a Google API, it must obtain an access token that grants access to that API.
There are several ways to make this request, and they vary based on the type of application you are building. Some requests require an authentication step where the user logs in with their Google account. User consent If the user grants the permission, the Google Authorization Server sends your application an access token (or an authorization code that your application can use to obtain an access token). 3. 4. Scenarios. Api - Google Reader OAuth mark as read.
ReaderAPI - pyrfeed - This is a RSS/Atom Reader and Framework. It use GoogleReader as a storage database. Note : This document is totally unofficial. You should not rely on anything on this document is you need an exact information. Google Reader API has not officially been released. This document has been made mainly by reverse engeneering the protocol. Google Reader API require : http client GET and POST support Cookie support https client https is only required for identification with Google to get the string called SID. Cookie support is only required to pass to all pages the current SID, proof of identification. Google Reader API may require : http client GET and POST support external tool to get SID (using https) putting SID into header SID : Session ID. Note : According to Mihai Parparita in Google Reader Support Group ( ), "Authentication is one of the reason why the API hasn't been released yet" . (!) The POST action will return you a text file, containing lines of the form : key=value Atom set of items.
Martin Doms : Using the Google Reader API – Part 1. Google Reader API series Google have never officially released API documentation for Google Reader, so this information is unofficial and subject to change. When I first started looking around for API docs to interface with Google Reader, this site seemed to be pretty much the only resource available. Unfortunately a lot of the information in that document is outdated, so I set about trying to figure out the API myself, with some success. To interface with Google reader, you’ll need to collect the following things from their authentication system: SID – A session ID, which remains valid until you log outToken – Similar to a session ID, but expires quickly.
Used to access direct API callsCookie – An ordinary cookie that uses your SID to authenticate your session on API calls The code samples I’m using will be in C#, but should be easily translatable to any language. Now that we have an SID we need a token. Name: SIDValue: [your SID]Path: /Domain: .google.com usingSystem.Net;usingSystem.IO; Reader-api - Google Reader API. Api-objectivec-client - Google APIs Client Library for Objective-C. Written by Google, this library is a flexible and efficient Objective-C framework for accessing JSON APIs. This is the recommended library for accessing JSON-based Google APIs for iOS and Mac OS X applications. The library is compatible with applications built for iOS 3 and later, and Mac OS X 10.5 and later. To get started with Google APIs and the Objective-C client library, read the introduction and study the example applications.
To browse the library source code, visit the Source tab. Generated interfaces for Google APIs are in the services folder. Library changes are documented in the release notes. Google APIs with generated interfaces include The library may also be used without generated interfaces with JSON REST and JSON-RPC APIs. If you have a problem or want a new feature to be included in the library, please join the discussion group. Externally-included projects: The library includes code from the separate projects GTM HTTP Fetcher, GTM OAuth 2, and json-framework. Objective c - Native Google Reader iPhone Application. Objective c - Using Google Reader API and OAuth in iPhone app.