Skip to main content
PATCH
/
feeds
/
{id}
Update feed settings
curl --request PATCH \
  --url https://api.juicer.io/v1/feeds/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "queue": true,
  "allowed": "<string>",
  "disallowed": "<string>",
  "profanity": true,
  "prevent_duplicates": true,
  "ai_moderation": true,
  "ai_harmful_content_filter": true,
  "ai_moderation_rules": "<string>",
  "ai_sentiment_filter": []
}
'
{
  "data": {
    "id": 123,
    "name": "<string>",
    "slug": "<string>",
    "sources_count": 123,
    "moderation": {
      "enabled": true,
      "allowed": "<string>",
      "disallowed": "<string>",
      "profanity_filter": true,
      "prevent_duplicates": true,
      "ai_moderation_available": true,
      "ai_moderation": true,
      "ai_harmful_content_filter": true,
      "ai_moderation_rules": "<string>",
      "ai_sentiment_filter": []
    },
    "created_at": "2023-11-07T05:31:56Z",
    "updated_at": "2023-11-07T05:31:56Z"
  }
}

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
​
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 keeps the post from whichever connected source is currently least represented in the feed so survivors rotate over time. 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