---
title: "Admin Articles Re Sanitize"
method: POST
path: "/v1/admin/articles/{slug}/re-sanitize"
---

# Admin Articles Re Sanitize

`POST /v1/admin/articles/{slug}/re-sanitize`

## 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/articles/{slug}/re-sanitize`
- Auth: none declared

Apply the current PII + newsletter-chrome sanitizer pipeline to
a single article's ``body_text`` and (optionally) enqueue a fresh
render-job so the listen catches up to the cleaned text.

Operator path for the post-hoc "MAY 14 / stray date stamp at top
of body" regression — articles ingested before the
newsletter-chrome strip landed still narrate the chrome literally.
A single curl against this endpoint per affected slug rewrites the
body + flushes audio.

## Path parameters

- `slug` string, required

## Headers

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

## Request body

- ReSanitizeArticleBody
  - `re_render` boolean

## 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)