> Markdown version of https://socialcannon.app/guides/rss-feed-and-recurring-posts-api (Recurring posts and RSS feeds with one API). The index of all SocialCannon documentation is at https://socialcannon.app/llms.txt.

# Recurring posts and RSS feeds with one API

Create a recurring series in your own time zone, or connect an RSS feed that writes a post for each new entry and waits for your review by default. Preview first and pause safely.

Updated 19 November 2026 · 8 min read

Some posting is the same job every week: a Monday tip, a Friday reminder, a link to each new article on your blog. SocialCannon has two automations for that work. A **recurring series** repeats a post on a daily, weekly or monthly rule. An **RSS feed** watches a feed address and turns each new entry into a post, after your review unless you choose otherwise. Both are plain REST calls, and the posts they create are ordinary posts that you can read, edit or delete like any other.

Recurring series and RSS feeds are enabled for each workspace separately. A workspace that does not have a feature enabled gets `404 FEATURE_DISABLED` and nothing is created; the [API reference](https://socialcannon.app/docs.md) gives the current status of both.

## Before you start

- A SocialCannon account and API credentials from **Settings → API Keys**. Both automations work on every plan, including [Free](https://socialcannon.app/pricing); the posts they create follow your plan’s usual limits.
- A bearer token with the `posts:read` and `posts:write` scopes. [Scheduling posts with one REST API](https://socialcannon.app/guides/schedule-social-media-posts-api.md) shows how to request one.
- The ID of the account to post to, from `GET /api/v1/accounts`, which needs the `accounts:read` scope. To try either automation without posting anywhere, use `sandbox` as the account ID.

## Recurring series

A series has an account, between 1 and 20 texts that are used in rotation, and a rule. The rule is written in your own time zone, so a 09:00 post stays at 09:00 when the clocks change.

## Step 1: Preview the rule

The preview stores nothing. It returns the next occurrences the rule would produce, with their UTC times, so you can check the rule before anything is created.

Preview a weekly rule

```
curl -X POST https://socialcannon.app/api/v1/series/preview \
  -H "Authorization: Bearer TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "rule": {
      "timezone": "Europe/London",
      "frequency": "weekly",
      "weekdays": ["MO", "TH"],
      "times": ["09:00"],
      "startDate": "2026-12-01"
    },
    "count": 5
  }'
```

## Step 2: Create the series

Create a series that posts on Mondays and Thursdays

```
curl -X POST https://socialcannon.app/api/v1/series \
  -H "Authorization: Bearer TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: weekly-tips-2026-12" \
  -d '{
    "accountId": "ACCOUNT_ID",
    "name": "Weekly tips",
    "contents": [
      "Tip 1: batch your posts for the week in one sitting.",
      "Tip 2: reply to comments within a day."
    ],
    "rule": {
      "timezone": "Europe/London",
      "frequency": "weekly",
      "weekdays": ["MO", "TH"],
      "times": ["09:00"],
      "startDate": "2026-12-01",
      "maxOccurrences": 20
    }
  }'
```

| Rule field | Accepted values |
| --- | --- |
| `timezone` | An IANA zone such as Europe/London |
| `frequency` | daily, weekly or monthly |
| `interval` | Optional, 1 to 12: every week, every second week and so on |
| `weekdays` | For weekly rules: MO, TU, WE, TH, FR, SA, SU |
| `monthDays` | For monthly rules: 1 to 31, or -1 for the last day of the month |
| `times` | One to four local times in 24-hour form, such as 09:00 |
| `startDate, endDate` | Dates as YYYY-MM-DD. endDate is optional and at most two years on |
| `maxOccurrences` | Optional, 1 to 1,000 |

About 24 hours before each occurrence, SocialCannon creates an ordinary scheduled post for it. From then on the post appears in `GET /api/v1/posts?status=scheduled`, and you can edit or delete it with the posts API. A workspace can have up to 25 active or paused series.

A series can carry media. Give `mediaUrls` as stable public https URLs that you host, because each occurrence gets its own copy; a series with media on a real account also needs the `media:upload` scope for as long as it runs.

## Step 3: Pause, resume or cancel

| Task | Request |
| --- | --- |
| List series | `GET /api/v1/series` |
| Read one, with its status and next occurrence | `GET /api/v1/series/SERIES_ID` |
| See each occurrence and its post | `GET /api/v1/series/SERIES_ID/occurrences` |
| Change the texts or the rule | `PATCH /api/v1/series/SERIES_ID with expectedRevision` |
| Pause | `POST /api/v1/series/SERIES_ID/pause` |
| Resume | `POST /api/v1/series/SERIES_ID/resume` |
| Stop for good | `POST /api/v1/series/SERIES_ID/cancel` |

Three rules are worth knowing before you rely on a series:

- **Pausing does not remove posts already scheduled.** Pause and cancel stop new occurrences, though one that was already being sent when the pause arrived can still create its post. A post the series has already created still publishes unless you delete it with the posts API, so check `GET /api/v1/posts?status=scheduled` afterwards.
- **Nothing is published late.** An occurrence more than 30 minutes late is recorded as missed and is never published late. After a resume, the series continues with occurrences at least five minutes ahead; one that came due during the pause is not sent.
- **Repeated refusals pause the series.** After three refused occurrences in a row, the series pauses and `lastError` gives the reason. Fix the cause, then resume.

## RSS feeds

A feed watches an RSS or Atom address and writes a post for each new entry from a template. The template can use `{title}`, `{link}` and `{summary}`. Feed posts are text only, so a feed can target Facebook, LinkedIn or X, and is refused with `FEED_ACCOUNT_UNSUPPORTED` for an account on a network that needs media on every post, such as Instagram, TikTok or YouTube.

## Step 1: Preview the feed

The preview fetches the feed once and returns its five newest entries as your template would write them. It stores nothing.

Preview a feed with a template

```
curl -X POST https://socialcannon.app/api/v1/feeds/preview \
  -H "Authorization: Bearer TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/blog/feed.xml",
    "template": "New on the blog: {title}\n\n{link}"
  }'
```

## Step 2: Create the feed and choose a mode

Create a feed in review mode

```
curl -X POST https://socialcannon.app/api/v1/feeds \
  -H "Authorization: Bearer TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: blog-feed-linkedin" \
  -d '{
    "url": "https://example.com/blog/feed.xml",
    "accountId": "ACCOUNT_ID",
    "mode": "review",
    "template": "New on the blog: {title}\n\n{link}"
  }'
```

The mode decides what happens when the feed finds a new entry.

| Mode | What happens to a new entry |
| --- | --- |
| `review` | The default. The entry waits until you approve or reject it. |
| `schedule` | A scheduled post is created delayMinutes after the entry is found (10 to 1,440, default 60), so you can delete it first. |
| `publish` | The entry is posted at once with no review. You must confirm this with "autoPublishAcknowledged": true. |

A feed is read every 60 minutes by default (`pollIntervalMinutes`, 15 to 1,440) and takes the newest `maxItemsPerPoll` new entries each time (1 to 10, default 3). Any other new entries found in the same read, and entries more than seven days old, are stored as `skipped` and are posted only if you approve them. Set the limit to the most entries your source publishes between reads. Entries that are already in the feed when you add it are not posted unless you set `backfillCount` (0 to 3, default 0). A workspace can have up to 20 feeds.

## Step 3: Review entries

1. List what is waiting with `GET /api/v1/feeds/FEED_ID/items?state=pending_review`.
2. Approve an entry with `POST /api/v1/feeds/FEED_ID/items/ITEM_ID/approve`. The body can carry edited `content`, or a `scheduledAt` up to 30 days ahead. Without a `scheduledAt` the post is sent at once, or `delayMinutes` after the approval while the feed is in `schedule` mode. Approving the same entry twice never posts twice.
3. Reject an entry you do not want with `POST /api/v1/feeds/FEED_ID/items/ITEM_ID/reject`.

Pause a feed with `POST /api/v1/feeds/FEED_ID/pause` and resume it with `POST /api/v1/feeds/FEED_ID/resume`. A send that was already in flight when the pause arrived can still create its post. Read the waiting entries with `GET /api/v1/feeds/FEED_ID/items?state=pending` before you resume, because entries that were queued before the pause are sent when the feed starts again, whatever mode the feed is in now and without further approval; in `schedule` or `publish` mode, new entries become posts as well. A feed that fails to load five times in a row, or meets a permanent failure such as a 404, moves to the `error` status with the reason in `lastError`; resume it after fixing the cause.

Start every feed in `review` mode. Move to `schedule` once the template reads well, and use `publish` only for a feed you control, because it posts whatever the feed contains.

## Use them from an AI assistant

The same automations are available as MCP tools: 6 for series and 7 for feeds, including `preview_series`, `create_series`, `preview_feed`, `create_feed` and `review_feed_entry`. The local MCP package adds them when `SOCIALCANNON_AUTOMATIONS_ENABLED` is set to `true` in its environment. An assistant can then set up “post this tip every Monday at 9:00” or “draft a LinkedIn post for each new blog article and show it to me first”. A series or feed keeps creating real posts on its own, so approve each create, resume and entry approval yourself. The [MCP guide](https://socialcannon.app/guides/mcp-server-social-media.md) covers the setup.

## Next steps

The [API reference](https://socialcannon.app/docs.md) documents every series and feed endpoint, and the [error reference](https://socialcannon.app/docs/errors.md) explains each refusal. If you are replacing a queue from another scheduler, [migrating from Buffer’s legacy API](https://socialcannon.app/guides/migrate-from-buffer-legacy-api.md) shows where series and feeds fit.

## Frequently asked questions

**Can I post automatically from an RSS feed?**

Yes. Create a feed with POST /api/v1/feeds and each new entry becomes a text post from your template. The default review mode waits for your approval; schedule mode creates a scheduled post after a delay; publish mode posts at once and must be confirmed with autoPublishAcknowledged.

**Which networks can an RSS feed post to?**

Facebook, LinkedIn and X, because feed posts are text only. X needs a paid plan. An account on a network that needs media on every post, such as Instagram, TikTok or YouTube, is refused with FEED_ACCOUNT_UNSUPPORTED.

**How do I repeat a post every week?**

Create a recurring series with POST /api/v1/series: give the account, between 1 and 20 texts used in rotation, and a rule with a time zone, a frequency of daily, weekly or monthly, the weekdays for a weekly rule, one to four local times and a start date. The guide shows a complete request. About 24 hours before each occurrence an ordinary scheduled post is created.

**Does pausing a series or feed cancel posts that are already scheduled?**

No. Pausing stops new occurrences and new feed entries. Posts that were already created are ordinary scheduled posts and still publish unless you delete them with the posts API, so check GET /api/v1/posts?status=scheduled after pausing.

**Do recurring series and RSS feeds need a paid plan?**

No. They work on every plan, and the posts they create follow your plan's usual limits, such as the number of connected accounts and paid-only publishing to X. A request that answers 404 FEATURE_DISABLED means the feature is not enabled for your workspace.
