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
¿No encuentras una película o serie? Inicia sesión para crearla:
¿Quieres puntuar o añadir este elemento a una lista?
¿No eres miembro?
Contestado por bkline
el 5 de julio de 2024 a las 09:22
Same problem for person 3250219, except this time the list of movies is empty.
Contestado por bkline
el 5 de julio de 2024 a las 09:34
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.Contestado por bkline
el 5 de julio de 2024 a las 10:16
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.Contestado por Travis Bell
el 5 de julio de 2024 a las 12:11
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.
Contestado por shanezor12
el 5 de julio de 2024 a las 12:55
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
Contestado por Travis Bell
el 5 de julio de 2024 a las 13:03
Yes, as soon as the item is purged from cache, everything will be fine.
Contestado por bkline
el 5 de julio de 2024 a las 13:32
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.Contestado por Travis Bell
el 5 de julio de 2024 a las 13:40
Thanks. And what about the response headers?
Contestado por bkline
el 5 de julio de 2024 a las 14:36
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):
Contestado por skrobs
el 5 de julio de 2024 a las 18:40
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 ! 😅