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 libraries from ProgrammableWeb's Library Directory that matched your search term. Although there many different interpretations of the word "library" among software developers, ProgrammableWeb adheres to a specific definition so as to clearly distinguish libraries from SDKs and frameworks in a way that will facilitate clean search results. In ProgrammableWeb's parlance, the term "library" is strictly used to describe a platform-specific software tool that, when installed, results in the provisioning a specific API. Conversely, SDKs are exclusively for consuming APIs and Frameworks are agnostic to specific APIs. If you think a library, SDK, API, or other asset is missing from our directory, be sure to check our guidelines for making contributions to ProgrammableWeb.