Complete references for major APIs are linked from this page. You may wish to start with Activating/Authenticating Access to FeedBurner APIs below, however, in order to verify you can access the APIs you require.
The FeedFlare API (FlareAPI) allows anyone to develop new FeedFlare units that tag, share, and interact with syndicated content, wherever it goes. Using FlareAPI to create new units can be as simple as displaying a link to related content, or as powerful as incorporating another web service. (English to Spanish translation of a blog posting, for example.)
FlareAPI is open to anyone and requires no registration or authentication to use. Get started with it today by studying these resources:
The FeedBurner Awareness API (AwAPI) allows publishers of FeedBurner feeds to reuse the detailed traffic statistics we capture for any of their feeds. Third-party applications and web services that consume feeds can leverage this data to provide useful feed awareness statistics to potential subscribers. FeedBurner captures traffic data at an overall level for every feed. Feeds that have item-level tracking enabled have access to much more detailed data at the individual item level. This data includes "resyndication" information, which is very useful for determining where and how a feed is being consumed.
Currently, the Feed Management API is offered only to Google partners who were previously under contract with FeedBurner. We are in the process of updating these APIs to be current with the features we provide, documenting the API better so that publishers can be self sufficient, and making sure the APIs are secure and cannot be abused. We are also looking at how to best support bulk management of feeds through our UIs and APIs in a future release.
In order to make use of FeedBurner APIs, you must understand how each is protected from unauthorized use. The Awareness API (AwAPI) uses authentication to permit only authorized users to modify feeds and view statistics info. In addition, AwAPI will retrieve statistics for specific feeds for any public request without authentication if the account owning those feeds has activated AwAPI support for those feeds.
Activating Public Access for AwAPI
By default, AwAPI access to FeedBurner feeds is only possible via authentication. You must activate public AwAPI for each feed to return traffic data to any anonymous public request (An example of which is Podnova's "FeedBurner Top 40".) To activate AwAPI, sign in to your FeedBurner account and visit the Publicize tab on the details page for the feed whose awareness data you want to access. Click Awareness API on the service menu that appears on the left side of the page. On the Awareness API form that appears, click Activate. FeedBurner will respond with a standard error on any attempt to access data for a feed that has not been activated. (See below for details on error codes.) If you don't wish to activate AwAPI statistics for general public consumption, you may instead use authenticated access to limit AwAPI access to your own, private use.
Using Authentication for Private AwAPI
We currently support two different mechanisms for user authentication: AuthSub for Web Applications, and ClientLogin for Installed Applications.
|
