# Legacy routes

> Old paths that still work but will be removed, and the route that replaces each one.

These paths keep answering exactly as before, so nothing you built breaks. They are no longer in the [API reference](https://cut.pro/docs/reference) and will be removed in the future: move to the new path when you can.

Every response from an old path carries two headers, as in [RFC 9745](https://www.rfc-editor.org/rfc/rfc9745): `Deprecation`, with the date it was superseded (`@1794960000` is November 18, 2026), and `Link` pointing to this page. Log them to find what is left to move.

| Old path | Use instead |
|---|---|
| `GET /clips` | `GET /videos` |
| `POST /clips/info` | `POST /videos/info` |
| `POST /clips` (with `video_id` in the body) | `POST /videos/{videoId}/submissions` |
| `GET /clips/{videoId}`, `DELETE /clips/{videoId}` | `GET /videos/{videoId}`, `DELETE /videos/{videoId}` |
| `/clips/{videoId}/...` (every route below a video) | `/videos/{videoId}/...` |
| `POST /personas/presets/{presetId}` | `POST /personas/presets/{presetId}/use` |

> The new paths take the same fields and return the same responses. The one difference is `POST /videos/{videoId}/submissions`: the video id goes in the URL instead of `video_id` in the body.

Paths below a monitor's broadcasts (`/monitors/{id}/broadcasts/{broadcastId}/clips/...`) are not legacy: there, `clips` are the clips themselves.
