The Movie Database Support
Support → API Support
Weird API request results
posted by Rissk13STAFFMOD on November 5, 2014 at 12:48 AM
I've been using the API for a few months now in a development environment. Today I started getting some weird results, such as the same movie for /movie/{id} no matter what id I pass in. I'm also getting different results for each of the /popular, /upcoming, /now_playing endpoints, as well as movies that came out 50 years ago for my search for movies that were released in the last 3 months (which previously worked before today). I haven't changed anything in my api calls so I'm not really sure what's going on. I just wanted to check to see if there were any known issues on the API side, or if in fact it is something on my side.
Also, the movie that's returning for the /movie/{id} call is Fight Club, every time. The apiary traffic inspector confirms that it's being called with different ids, but always returns Fight Club. Let me know if you want me to post the requests.
Thanks for any info.
Reply by Filimindji
on November 5, 2014 at 3:23 AM
Same issue here. The result is always Fight Club.
Any clue about that ?
Reply by Travis Bell
on November 5, 2014 at 10:56 AM
It sounds to me like you guys are hitting the Apiary with the "Mock Server" host setting.
You can see if you call the production API everything is being returned properly:
If you want to be able to use Apiary to test real world responses, you need to switch the "Host" in Apiary to "Debugging Proxy".
Cheers.
Reply by Rissk13
on November 5, 2014 at 11:45 AM
Weird, it was using the real API before yesterday and I was using this url "http://private-key-themovietb.apiary.io/3/movie/id". Looking at the 3 different possible urls in Apiary, it doesn't seem like this is valid anymore? Changing it to the production url works. Thanks
Reply by Travis Bell
on November 5, 2014 at 11:55 AM
Hi Rissk13,
I can't answer that, perhaps it's a bug and/or something they changed? Probably best to contact Apiary to see what changed.
Please note, you should only ever be using Apiary for testing. Our production URL is the only one we support and Apiary is not designed to handle a real world production load.
Cheers.
Reply by Filimindji
on November 19, 2014 at 4:17 AM
Thank you, we changed to the prod url and it's fine now.