Feedbin API V2 Documentation

Entries are paginated with a limit of 100 items per page.

Link Headers

Paginated responses include a Links header containing URLs for navigating the result set. The supported rel values are:

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

Total Record Count

The response header X-Feedbin-Record-Count provides the total number of records available for that resource.

Links: <https://api.feedbin.com/v2/feeds/1/entries.json?page=2>; rel="next", <https://api.feedbin.com/v2/feeds/1/entries.json?page=5>; rel="last"
X-Feedbin-Record-Count: 500

The Feedbin API uses the ISO 8601 date format. All requests and responses must adhere to this specification.

Precision and the since parameter

Dates are high-resolution. When using the since parameter to fetch updates, use the exact date string returned by the server from your previous request. Do not round down to the nearest second, as this will likely cause duplicate entries in your results.

Format Example

YYYY-MM-DDThh:mm:ss.ssssssTZD

• UTC: 2013-02-19T15:33:38.449047Z
• With Timezone: 2013-02-19T07:33:38.449047-08:00

When using the mode=extended parameter on subscription endpoints, the API includes a json_feed key in the response. This key contains additional metadata following the JSON Feed specification, such as favicon, icon, and home_page_url.

{
  "id" : 1,
  "feed_id" : 1,
  "site_url" : "https://micro.blog/",
  "title" : "Micro.blog - manton timeline",
  "feed_url" : "https://micro.blog/feeds/manton.json",
  "created_at" : "2019-05-23T23:49:14.487938Z",
  "json_feed" : {
    "favicon" : "https://micro.blog/images/icons/favicon_32.png",
    "feed_url" : "https://micro.blog/feeds/manton.json",
    "icon" : "https://micro.blog/images/icons/favicon_256.png",
    "version" : "https://jsonfeed.org/version/1",
    "home_page_url" : "https://micro.blog/",
    "title" : "Micro.blog - manton timeline"
  }
}

While Feedbin supports Twitter subscriptions automatically, you can build a custom Twitter experience by combining Feedbin data with the Twitter API. Because Twitter's terms of service prohibit redistributing their API data, you should use Feedbin to discover tweet IDs and then use your own Twitter developer credentials to fetch the full tweet content.

To implement this flow:

1. Register an application on the Twitter developer site.
2. Implement a Twitter authentication flow in your application to fetch data on behalf of your users.
3. Fetch entries from Feedbin using mode=extended to retrieve the necessary Twitter identifiers.
4. Use Twitter's statuses/lookup API to bulk load the actual tweet content using the IDs provided by Feedbin.

To improve speed and reduce load, use HTTP caching. GET requests return ETag and Last-Modified headers.

In subsequent requests, include these values in the If-None-Match and If-Modified-Since headers respectively. If the resource has not changed, the server will return a 304 Not Modified response.

# 1. Initial request to get headers
curl -v -u 'example@example.com:password' https://api.feedbin.com/v2/subscriptions/3.json
# Look for ETag and Last-Modified in response

# 2. Subsequent request using those headers
curl -v -u 'example@example.com:password' \
--header 'If-Modified-Since:Sat, 02 Feb 2013 15:20:46 GMT' \
--header 'If-None-Match:"c7d001e87bda1f0d3745b6bd2811b055"' \
https://api.feedbin.com/v2/subscriptions/3.json

To authenticate requests to the Feedbin API, you must use HTTP Basic Authentication. You can provide your credentials (email and password) via the Authorization header or by using the built-in support in your HTTP library.

A common way to verify if a user's credentials are valid is to call the GET /v2/authentication.json endpoint.

curl --request GET --user "example@example.com:password" https://api.feedbin.com/v2/authentication.json

The Feedbin API is a REST-style API. All requests must use https. The base URL is https://api.feedbin.com/v2/.

Authentication

The API uses HTTP Basic authentication. You can authenticate using your email and password.

Content-Type Header

When creating or updating a record (e.g., using POST or PATCH), you must set the Content-Type header to application/json; charset=utf-8. Failure to include this header will result in a 415 Unsupported Media Type error.

# Basic GET request
curl -u 'example@example.com:password' https://api.feedbin.com/v2/subscriptions.json

# POST request with required Content-Type header
curl -u 'example@example.com:password' \
-H "Content-Type: application/json; charset=utf-8" \
-X POST -d '{"feed_url":"http://daringfireball.net"}' \
https://api.feedbin.com/v2/subscriptions.json

When working in Objective-C, ensure you force a specific locale (e.g., en_US) and timezone to prevent unexpected formatting based on the user's region.

```objectivec
NSDateFormatter *feedbinDateFormatter = [[NSDateFormatter alloc] init];
feedbinDateFormatter.timeZone = [NSTimeZone timeZoneWithAbbreviation:@