Skip to main content

Resolve a link request into the concrete `series.id` it targets, shared by the single-release [`link`] handler and the [`bulk_link`] action. The `posted_at` anchor is only consulted on the provider path, where it seeds the freshly-upserted series' first-seen timestamp; callers pass the release's own `posted_at` (single link) or the anchor release's (bulk). Bulk-link a set of review-queue releases to one series. The body's `ids` (intersected with the queue statuses) select the releases; the series is named exactly as in the single-release [`link`] handler. Each release is linked individually (clearing its candidates and bumping the series' highest volume/chapter marks) so the result matches what N single links would produce. The operator is responsible for the selection being one series' releases; the endpoint links them blindly to the chosen target.

POST 
/api/v1/releases/bulk/link

Resolve a link request into the concrete series.id it targets, shared by the single-release [link] handler and the [bulk_link] action. The posted_at anchor is only consulted on the provider path, where it seeds the freshly-upserted series' first-seen timestamp; callers pass the release's own posted_at (single link) or the anchor release's (bulk). Bulk-link a set of review-queue releases to one series. The body's ids (intersected with the queue statuses) select the releases; the series is named exactly as in the single-release [link] handler. Each release is linked individually (clearing its candidates and bumping the series' highest volume/chapter marks) so the result matches what N single links would produce. The operator is responsible for the selection being one series' releases; the endpoint links them blindly to the chosen target.

Request​

Responses​