starred/Radarr

Fork 0

mirror of https://github.com/Radarr/Radarr.git synced 2026-03-02 22:57:34 -05:00

MovieLookup API call not producing "id" key:value pair #9235

New issue

Open

opened 2026-02-20 00:11:53 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 00:11:53 -05:00

Owner

Originally created by @artstar-es on GitHub (Jul 29, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Version 5.26.2.10099 has a bug where running the Movie Lookup query API results in the "id" key:value pair not being produced.

API call: https://[redacted]/radarr/api/v3/movie/lookup/tmdb?tmdbId=1071585&apikey=[redacted]

What it should look like:

{
  "id": 0,
  "title": "string",
  "originalTitle": "string",
  "originalLanguage": {
    "id": 0,
    "name": "string"
  },

What it actually produces:

{
  "title": "M3GAN 2.0",
  "originalTitle": "M3GAN 2.0",
  "originalLanguage": {
    "id": 1,
    "name": "English"
  },

Expected Behavior

Per the documentation in https://radarr.video/docs/api/#/MovieLookup/get_api_v3_movie_lookup_tmdb

It should be producing the "id" key:value pair but it does not appear at all, with the resulting output starting from the "title" key:value pair instead.

Steps To Reproduce

No response

Environment

- OS: Debian 6.1.90
- Radarr: 5.26.2.10099 (5.26.2.10099-ls279 by linuxserver.io)
- Docker Install: Yes
- Using Reverse Proxy: Yes 
- Browser: python API call
- Database: Sqlite 3.49.2

What branch are you running?

Master

Trace Logs? Not Optional

radarr.trace.0.txt

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @artstar-es on GitHub (Jul 29, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior Version 5.26.2.10099 has a bug where running the Movie Lookup query API results in the "id" key:value pair not being produced. API call: https://[redacted]/radarr/api/v3/movie/lookup/tmdb?tmdbId=1071585&apikey=[redacted] What it should look like: ``` { "id": 0, "title": "string", "originalTitle": "string", "originalLanguage": { "id": 0, "name": "string" }, ``` What it actually produces: ``` { "title": "M3GAN 2.0", "originalTitle": "M3GAN 2.0", "originalLanguage": { "id": 1, "name": "English" }, ``` ### Expected Behavior Per the documentation in https://radarr.video/docs/api/#/MovieLookup/get_api_v3_movie_lookup_tmdb It should be producing the "id" key:value pair but it does not appear at all, with the resulting output starting from the "title" key:value pair instead. ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: Debian 6.1.90 - Radarr: 5.26.2.10099 (5.26.2.10099-ls279 by linuxserver.io) - Docker Install: Yes - Using Reverse Proxy: Yes - Browser: python API call - Database: Sqlite 3.49.2 ``` ### What branch are you running? Master ### Trace Logs? **Not Optional** [radarr.trace.0.txt](https://github.com/user-attachments/files/21489029/radarr.trace.0.txt) ### Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman added the

labels

2026-02-20 00:11:53 -05:00

deekerman commented

2026-02-20 00:11:53 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jul 29, 2025):

The "Id" is the radarr internal id which would only be returned with the movie object was added to radarr.

@bakerboy448 commented on GitHub (Jul 29, 2025): The "Id" is the radarr internal id which would only be returned with the movie object was added to radarr.

deekerman commented

2026-02-20 00:11:53 -05:00

Author

Owner

@artstar-es commented on GitHub (Jul 29, 2025):

Thanks for the prompt reply!!

Yes, that is the id I am expecting to be returned, for the purposes of a Python automation intended to unmonitor Radarr entries based on their played/watched status in Emby.

The returned payload has everything in it except for that Radarr ID.

@artstar-es commented on GitHub (Jul 29, 2025): Thanks for the prompt reply!! Yes, that is the id I am expecting to be returned, for the purposes of a Python automation intended to unmonitor Radarr entries based on their played/watched status in Emby. The returned payload has everything in it except for that Radarr ID.