---
title: "Record Visual Subject Readiness"
method: POST
path: "/internal/editorial/visual-subject-readiness"
tags: ["editorial feed"]
---

# Record Visual Subject Readiness

`POST /internal/editorial/visual-subject-readiness`

## Request

- Base URL: `https://api.tickertrac.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.tickertrac.com/internal/editorial/visual-subject-readiness`
- Auth: API key in header `X-API-Key`

Record whether Editorial can render each ticker. No user data is touched.

Reported rather than queried: Editorial's store is a local SQLite file this container
cannot reach, so the only honest direction is the one that already carries artifact
registration.

## Request body

- VisualSubjectReadinessIn: One boolean per ticker, and deliberately nothing else. Editorial holds scene direction, palette and concept assets for each subject. None of that belongs here; what this side needs is only whether a candidate on that ticker can be rendered, so that a weekly admin reminder stops counting impossible work as pending. `extra="forbid"` is what keeps a well-meaning future field from widening that.
  - `subjects` VisualSubjectReadinessItem[], required
    - `ticker` string, required
    - `has_visual_subject` boolean, required

## Response `200`

Successful Response

- VisualSubjectReadinessOut
  - `recorded` integer, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/tickertrac/apis/tickerrag-api.md) · [All operations](https://skmtc.dev/tickertrac/apis/tickerrag-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tickertrac/apis/tickerrag-api/revisions/3c7eb0f6425d?raw)