Outdated Openapi Yaml file ?
Author: BillosCreated Jul 27, 2026Updated Sep 18, 2026
Labelsconfirmed
Description
Hello, I have been using the yaml file to generate a quick Typescript SDK.
I'm currently trying to use the POST /api/v1/watchlist, with the following parameters => { tmdbId: 1422 }
I can use the following fields :
export type WatchlistWritable = {
tmdbId?: number;
ratingKey?: string;
type?: string;
title?: string;
media?: MediaInfoWritable;
requestedBy?: UserWritable;
};This matches what the yaml file describe.
But the response I'm getting from the Seerr backend is :
ℹ Error: [
{
"code": "invalid_value",
"values": [
"movie",
"tv"
],
"path": [
"mediaType"
],
"message": "Invalid option: expected one of \"movie\"|\"tv\""
}
]I think the Yaml file is simply outdated compared to the real APIs.
Version
3.3.0
Steps to Reproduce
Simple curl should do the trick
curl -L 'https://seerr.domain.net/api/v1/watchlist' -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'X-Api-Key: xxxxxxxxxxxxx' -d '{ "tmdbId": 1422 }'Screenshots
No response
Logs
Platform
desktop
Database
PostgreSQL
Device
Desktop
Operating System
Kubuntu 26.04
Browser
Firefox
Additional Context
No response
Search Existing Issues
- Yes, I have searched existing issues.
Code of Conduct
- I agree to follow Seerr's Code of Conduct
Source: seerr-team/seerr