When I submit https://api.themoviedb.org/3/person/4197304?api_key=..... I get back a sequence of movie records instead of the person record for the actor Rebekah Cobaugh.
Oddly, there doesn't seem to be a widget for attaching a screenshot to this ticket, so I've put the screenshot on my own server
Kan ’n rolprent of TV-program nie vind nie? Teken aan om dit te skep.
Wil u hierdie item gradeer of tot ’n lys toevoeg?
Nie ’n lid nie?
Antwoord deur bkline
op 5 Julie 2024 om 9:22 VM
Same problem for person 3250219, except this time the list of movies is empty.
Antwoord deur bkline
op 5 Julie 2024 om 9:34 VM
Here's another interesting data point. When I use the same URL with
curl
I get the correct person record. But when invoked from Python code (using therequests
third-party library) or from the browser (Chrome, Edge, Safari, doesn't matter), I get back the bogus response with the (sometimes empty) list of movies. Also, I should note that for most person records, the API is returning the appropriate person records to the Python script, so it's not like the APIs are completely broken globally. But something is definitely broken somewhere.Antwoord deur bkline
op 5 Julie 2024 om 10:16 VM
Here are some other person IDs for which the API returns the wrong response.
All of the other bogus records had the same structure illustrated above, with the
results
sequence of abbreviated movie records, but the response for person 77464 (Sean Douglas) had a different structure:... which looks like an
external_ids
record.Antwoord deur Travis Bell
op 5 Julie 2024 om 12:11 NM
Hi @bkline,
Indeed, when we execute our database maintenance, this issue happens from time to time. Not sure the cause of it yet, but I've been spending some time trying to figure it out.
I would be curious to see the response headers of each of those requests if they are still returning different payloads.
Antwoord deur shanezor12
op 5 Julie 2024 om 12:55 NM
I am also experiencing this issue this morning, I will be requesting Movie Details and get back what looks like a Discover response or External IDs response, but only happens very rarely, but seems stuck at least for a while. I had one happen last night, and when I tried it again this morning it worked as expected
gives me this response
Antwoord deur Travis Bell
op 5 Julie 2024 om 1:03 NM
Yes, as soon as the item is purged from cache, everything will be fine.
Antwoord deur bkline
op 5 Julie 2024 om 1:32 NM
Hi, @travisbell. I'm surprised you're not able to reproduce the failures yourself. I assume that means the unexpected behavior is sensitive to the
api_key
value.Headers from
curl
:Headers from Chrome:
Headers from Edge:
Headers from Safari:
Headers from Postman:
Only
curl
gets the correct response. All the others (including Postman) get a bogus response.Antwoord deur Travis Bell
op 5 Julie 2024 om 1:40 NM
Thanks. And what about the response headers?
Antwoord deur bkline
op 5 Julie 2024 om 2:36 NM
Ah, right. Looking back, I see that this is what you asked for, not the request headers. Apologies. 😊
Headers received when the response is correct (curl):
Headers received when response is bogus (Safari):
Another failure (Python script):
Antwoord deur skrobs
op 5 Julie 2024 om 6:40 NM
I'm also getting strange results from time to time, from all points (/movie/, /tv/ ...)
Eg, url
https://api.themoviedb.org/3/person/1615007?api_key=APIKEY&append_to_response=images,external_ids
give me:keywords
should not be here. If i removeexternal_ids
from url, the result is correct, but without ... the needed external ids ! 😅