Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time

Feedbin API V2

This is the official documentation for the Feedbin REST-style API.

API Objects

Tech Notes


Making Requests

The base URL for all requests is Only https is supported.

The Feedbin API uses HTTP Basic authentication

Using cURL you would make a request like:

curl -u ''

When creating or updating a record you must set application/json; charset=utf-8 as the Content-Type header.

curl -u '' \
-H "Content-Type: application/json; charset=utf-8" \
-X POST -d '{"feed_url":""}' \

Without this header you'll wind up with a 415 Unsupported Media Type response.

HTTP Caching, Use It

For extra speed, please use HTTP Caching. GET request set ETag and a Last-Modified headers.

curl -v -u ''
< ETag: "c7d001e87bda1f0d3745b6bd2811b055"
< Last-Modified: Sat, 02 Feb 2013 15:20:46 GMT

You can use these headers in subsequent requests like:

curl -v -u '' --header 'If-Modified-Since:Sat, 02 Feb 2013 15:20:46 GMT' --header 'If-None-Match:"c7d001e87bda1f0d3745b6bd2811b055"'
< HTTP/1.1 304 Not Modified


Entries use pagination. Each page has a limit of 100 items. Paginated request will include a link header like:

Links: <>; rel="next", <>; rel="last"

The possible rel values are:

  • first The URL of the first page of results.
  • prev The URL of the previous page of results.
  • next The URL of the next page of results.
  • last The URL of the last page of results.

On paginated resources there is a header in the response called: X-Feedbin-Record-Count. This header reports the total number of records for a resource.


The Feedbin API uses the ISO 8601 date format. All responses will include dates formatted to this spec and all requests should stick to it as well. The dates are as high resolution as possible to allow for rapid state changes. When using the since parameter it is best to include the date exactly as it was returned by the server when the last request was made. Rounding down to the nearest second will most likely cause duplicates.

The date should include complete date plus hours, minutes, seconds and timezone YYYY-MM-DDThh:mm:ss.ssssssTZD (eg 2013-02-19T07:33:38.449047-08:00 or in UTC 2013-02-19T15:33:38.449047Z). All dates will be converted to UTC, so the timezone is very important.


In Objective-C it's important to force a locale for the date because different regions can cause unexpected output. For example you can properly format a date for the Feedbin API like:

NSDateFormatter *feedbinDateFormatter = [[NSDateFormatter alloc] init];
feedbinDateFormatter.timeZone = [NSTimeZone timeZoneWithAbbreviation:@"GMT"];
[feedbinDateFormatter setDateFormat:@"yyyy-MM-dd'T'HH:mm:ss.SSSSSS'Z'"];
[feedbinDateFormatter setLocale:[[NSLocale alloc] initWithLocaleIdentifier:@"en_US"]];

Thanks to Stefan Pauwels for sharing this tip.


Until 2014-03-14 the API hostname was will remain available but is recommended because it is the new primary domain.


Feedbin API Documentation






No releases published


No packages published