---
title: "Admin Patch Intake Source"
method: PATCH
path: "/v1/admin/intake/sources/{source_id}"
tags: ["publisher-shows"]
---

# Admin Patch Intake Source

`PATCH /v1/admin/intake/sources/{source_id}`

## Request

- Base URL: `https://api.storyflo.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.storyflo.com/v1/admin/intake/sources/{source_id}`
- Auth: none declared

Operator repair for a single IntakeSource.

``default_vertical`` exists because prod runs
``INTAKE_PRIORITY_VERTICALS_ONLY=1``: a source whose vertical is NULL or
not a ``PODCAST_VERTICAL_META`` key has EVERY article silently skipped
(``app.intake.worker._passes_priority_vertical``). Such a row is
indistinguishable from a healthy one — active, polled on schedule,
``last_error`` NULL — while producing nothing, for as long as nobody
notices. Onboard has derived a valid vertical since 2026-07-16 and
``repair_active_source_verticals`` can sweep the backlog, but there was
no way to fix ONE named source without a shell inside the VPC. That gap
is why a live publisher's feed sat active and empty for 23 days.

``show_name`` is the per-source title — the same field the
publisher-facing rename writes.

## Path parameters

- `source_id` string, required

## Headers

- `x-storyflo-email-token` string, nullable

## Request body

- IntakeSourcePatch
  - `default_vertical` string, nullable
  - `show_name` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/storyflo/apis/storyflo-inference-router.md) · [All operations](https://skmtc.dev/storyflo/apis/storyflo-inference-router/llms.txt) · [OpenAPI document](https://skmtc.dev/storyflo/apis/storyflo-inference-router/revisions/c3a1a735ac7a?raw)