Curator API: Create a Source
POST https://api.curator.io/v1/sources adds a source to one of your feeds and loads its first posts. The request needs your API key, and your plan must include API access. Only HTTPS is supported.
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). You can only add sources to feeds in the account the key belongs to.
Example request
curl -X POST "https://api.curator.io/v1/sources?api_key=API_KEY" \
-d "feed_id=FEED_ID" \
-d "source_type=16" \
-d "tag=https://www.curator.io/blog/rss"Parameters
Parameter | Description |
|---|---|
| The API ID of the feed to add the source to. The public key is not accepted here. |
| The source type ID, an integer from the source types table below. |
| What to pull posts from, up to 200 characters: an account handle, hashtag, search term, or URL, depending on the source type. |
| Display name for the source. When left out, Curator names the source for you. |
| URL of an image to show as the author image on this source's posts. |
Response
Adding a source loads its first posts straight away, so the request can take a few seconds. On success, the response is the new source object (described in Get Sources) with a response field added:
{
"id": "SOURCE_ID",
"feed_id": "FEED_ID",
"source_type": 16,
"tag": "https://www.curator.io/blog/rss",
"status": "active",
...
"response": { "success": true, "message": "12 posts were added to your feed" }
}If the first load fails, the source is removed again and the response is a 200 with an error body instead of a source object:
{ "success": false, "error": true, "message": "Loading posts failed with - REASON" }Always check for "error": true before treating the source as added. When the failure is caused by an expired connection, the message is Loading posts failed: connection is not longer valid and the connection is disabled until you reconnect it in the Curator Dashboard.
Source types
Source types marked "Needs a connection" only work after you connect that network's account under Connections in the Curator Dashboard. Without one, adding the source returns a 422 with a link to the Connections page.
ID | Source type | Needs a connection |
|---|---|---|
1 | Twitter Hashtag | Yes |
3 | Twitter User | Yes |
5 | Facebook Page | Yes |
7 | Pinterest User | No |
9 | Flickr Hashtag | No |
10 | YouTube Hashtag | No |
11 | Tumblr Hashtag | No |
13 | YouTube Channel | No |
14 | Tumblr User | No |
15 | Flickr User | No |
16 | RSS | No |
27 | Flickr Album | No |
28 | Vimeo Tag | No |
32 | Glassdoor Employer Reviews | No |
33 | Instagram Business Account | Yes |
34 | Instagram Account | Yes |
35 | YouTube Playlist | No |
38 | Instagram Business Hashtag | Yes |
39 | Yelp Business Reviews | No |
40 | DeviantArt User Gallery | No |
41 | Behance Project | No |
43 | Slack Channel Feed | Yes |
45 | Giphy Search | No |
46 | Instagram Business Mention | Yes |
47 | Instagram Stories | Yes |
48 | Reddit Subreddit Feed | Yes |
49 | Reddit User Feed | Yes |
51 | TikTok User Videos | Yes |
54 | Instagram Tagged Business / Collab Posts | Yes |
55 | Facebook Page Mention | Yes |
56 | LinkedIn Company Page | No |
57 | TikTok Hashtag | Yes |
58 | Google Reviews (Lite) | No |
59 | Google Reviews | No |
60 | Threads User | Yes |
61 | Threads Mentions | Yes |
62 | LinkedIn Profile Page | No |
Some source types also depend on your plan, such as TikTok Hashtag, Google Reviews, and LinkedIn, which have their own limits.
Errors
Status | When | Body |
|---|---|---|
401 | The API key is missing or not valid. |
|
403 | Your plan does not include API access, you have reached a source limit, the source type is not on your plan, or your subscription is paused. |
|
422 | A required parameter is missing or invalid, the feed or source type was not found, the source type is not active, or the source type needs a connection you have not added. |
|
429 | When rate limiting is enabled, more than 60 requests per minute. |
|