Curator API: Get Feeds
GET https://api.curator.io/v1/feeds returns every feed in your Curator account as JSON. The request needs your API key, and your plan must include API access. Only HTTPS is supported.
To read the posts in a feed, use GET https://api.curator.io/v1/feeds/FEED_ID/posts, covered in Get Posts. GET https://api.curator.io/v1/feeds/FEED_ID is an alias of that endpoint and returns posts, not the feed's settings.
Authentication
Send your Curator API key (find it in the Curator Dashboard) in one of three ways: as a query string (?api_key=API_KEY), as a Basic auth header with the API key as the username, or as a Bearer token (Authorization: Bearer API_KEY). The key decides which account you are working in; you only see that account's feeds.
Example request
curl "https://api.curator.io/v1/feeds?api_key=API_KEY"Response
A 200 response is a JSON array of feed objects, with no wrapper and no pagination.
Feed object
Feed objects include the fields below, plus widget configuration fields that the Curator Dashboard manages.
Field | Description |
|---|---|
| The feed's API ID (a UUID). Use it as |
| The feed's public key, used by the embed code and accepted by |
| Feed name. |
| URL-friendly version of the name. |
| Status new posts get: |
| The feed's widget layout and theme. |
| Number of posts in the feed. |
| Whether API responses for the feed are cached, and for how many minutes. |
| Whether the feed's embedded widget has loaded posts at least once. |
| Whether the feed uses the current widget version. |
Errors
Status | When | Body |
|---|---|---|
401 | The API key is missing or not valid. |
|
403 | Your plan does not include API access. |
|
429 | When rate limiting is enabled, more than 60 requests per minute. |
|