Skip to main content
PATCH
Update feed settings

Authorizations

Authorization
string
header
required

API key prefixed with jcr_. To obtain a key programmatically (no dashboard required), see POST /v1/authorize.

Path Parameters

id
integer
required

Body

application/json
name
string
sync_interval
integer | null

How often the feed's sources are synced, in minutes. Allowed values are the standard sync frequencies 1, 5, 10, 30, 60, 240, and 1440 (once a day). Use 0 to archive the feed (stop updating it). Send null or an empty value to clear the override and fall back to your plan's default sync frequency (once a day on most plans). Setting it requires a plan that supports per-feed sync frequency; on other plans the request returns 422 with error.code = "sync_interval_not_available". On credit-metered API plans an invalid value is rejected with 422 (error.code = "invalid_sync_interval"). On credit-metered API plans each successful sync of a metered source consumes API credits, so a faster interval consumes credits proportionally faster (an hourly feed spends roughly 24x what a daily feed does); when the balance runs out the feed's sources pause until it is topped up.

queue
boolean

Enable moderation queue

allowed
string

Comma-separated whitelist terms

disallowed
string

Comma-separated blacklist terms

profanity
boolean

Enable profanity filter

prevent_duplicates
boolean

Enable duplicate post prevention

deduplication_strategy
enum<string>

Which post survives when duplicates are detected. prioritize_top_source keeps the post from the highest-priority source (lowest position). distribute_across_sources spreads the survivors across the feed's sources, so no one source wins every duplicate. It balances which source survives each set of duplicates, not the feed's overall share per source. Only meaningful when prevent_duplicates is true.

Available options:
prioritize_top_source,
distribute_across_sources
ai_moderation
boolean

Master switch for AI moderation. When enabled, new posts are queued and evaluated by AI before going live. Requires at least one AI sub-filter (ai_harmful_content_filter, ai_moderation_rules, or ai_sentiment_filter) to take effect. Requires the Pro plan or higher.

ai_harmful_content_filter
boolean

Check posts against the OpenAI moderation API and hold any flagged for harmful content (hate, violence, sexual, etc.).

ai_moderation_rules
string | null

Natural-language rules the AI applies when deciding whether to keep a post (e.g. "Only show posts about coffee").

ai_sentiment_filter
enum<string>[]

Allowed post sentiments. Posts whose AI-classified sentiment is not in this list are held in the moderation queue. An empty array disables sentiment filtering.

Available options:
positive,
neutral,
negative

Response

Feed updated

data
object