FeedBurner offers developers an established library of APIs for interacting with the service. FeedBurner is a web feed management provider that provides custom RSS feeds and management tools to bloggers, podcasters, and other web-based content publishers. Using the features this library provides, anyone with a FeedBurner account may perform some of the most common actions available on the service programmatically.
Currently the library contains three APIs:
The FeedFlare API 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.
The FeedBurner Awareness API allows publishers of FeedBurner feeds to reuse the detailed traffic statistics captured for any of their feeds. Third-party applications and web services that consume feeds can leverage this data to provide 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.
The FeedBurner Management API allows publishers of FeedBurner feeds to create and manage feeds within their FeedBurner accounts. Currently, the Feed Management API is offered only to Google partners who were previously under contract with FeedBurner.
FeedBurner web services use the REST protocol to receive requests and return data over HTTP. Data is exchanged as plain text XML which can be repurposed, transformed, and displayed by applications that you build.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at email@example.com
22-08-18 15:31:27[Mashup] PropRover updated with Related API FeedBurner
17-01-17 18:11:26Deadpooled API
11-06-15 03:32:35[Mashup] UniDAC updated with Related API FeedBurner
04-03-15 13:05:52[Mashup] Panoraudio updated with Related API FeedBurner
28-02-15 01:22:08[Mashup] ResortsNearDelhi.com updated with Related API FeedBurner
12-11-14 15:49:23[Sample Source Code] Design and code an integrated Facebook app updated with Related API FeedBurner