I don't imagine it would. I assume you guys are developing on v3 since you are relatively new here. We haven't pushed users to 2.1 since around January of 2012.
To double check this you can take a look at your request URLs. If they are http://api.themoviedb.org/3/* you have nothing to worry about.
There's cURL examples on the documentation website. Click any of the methods and you'll see the example response drop down. From there choose cURL from the "Show code sample" drop down. They'll give you a mock Apiary call, just swap that out with api.themoviedb.org for the real world, production server.
I think it's working now for I missed the "3" (see my prev pot), now I just need to take care of the JSON instead of previous XML parser in my Java code.
By the way, do you also support XML in ver. 3 now ?
Travis Bell 的回复
于 2013 年 05 月 15 日 9:22上午
Hi kmplayer,
I don't imagine it would. I assume you guys are developing on v3 since you are relatively new here. We haven't pushed users to 2.1 since around January of 2012.
To double check this you can take a look at your request URLs. If they are http://api.themoviedb.org/3/* you have nothing to worry about.
joshuahotw 的回复
于 2013 年 09 月 24 日 1:09上午
Hi there, I used to be able to perform search results of list item by accessing moviedbapi with the following string in my application: http://api.themoviedb.org/2.1/Movie.search/en/xml/api_key/Superman
However, recently I found that the errors occurred as following, should it be changed due to v3 api and what the sting should be like? Error 202 for URL http://api.themoviedb.org/2.1/Movie.search/en/xml/api_key/Superman
Thanks.
Travis Bell 的回复
于 2013 年 09 月 24 日 10:14上午
Hi joshuahotw,
2.1 was shut down on September 15 so you will have to update your app to use v3. The docs are here.
joshuahotw 的回复
于 2013 年 09 月 24 日 11:29上午
Hi Travis,
Yes, I try to use "http://api.themoviedb.org/3/search/movie?api_key=my-api-key&query=batman" and it does work in curl, however, I see 406 error in my code when using it. Do you have any example for that to avoid 406 result? Thanks.
JH
Travis Bell 的回复
于 2013 年 09 月 24 日 11:45上午
You need to set an
Accept
header.There's cURL examples on the documentation website. Click any of the methods and you'll see the example response drop down. From there choose cURL from the "Show code sample" drop down. They'll give you a mock Apiary call, just swap that out with api.themoviedb.org for the real world, production server.
Cheers.
joshuahotw 的回复
于 2013 年 09 月 24 日 12:23下午
Travis,
Yes, I have set the header in Java program:
HttpGet getRequest = new HttpGet(url); getRequest.setHeader("Accept", "application/json"); W/HttpRetriever(577): Error 404 for URL http://private-6a2c7-themoviedb.apiary.io/search/movie?api_key=4a8772166b67d7xxxxxxxxx&query=moon
Any idea ?
JH
Travis Bell 的回复
于 2013 年 09 月 24 日 12:46下午
Hi Joshua,
That's a 404 now. Not sure. The query works as expected in production, so I might chalk that up to a issue with Apiary.
joshuahotw 的回复
于 2013 年 09 月 24 日 12:49下午
Travis,
I think it's working now for I missed the "3" (see my prev pot), now I just need to take care of the JSON instead of previous XML parser in my Java code. By the way, do you also support XML in ver. 3 now ?
Joshua
Travis Bell 的回复
于 2013 年 09 月 24 日 12:51下午
Cool. Indeed, typo!
No, v3 is JSON only.
Cheers.
joshuahotw 的回复
于 2013 年 09 月 29 日 2:50下午
Travis, for the image link, what is the server info for them ? Thanks a lot for your input.
Travis Bell 的回复
于 2013 年 09 月 29 日 3:54下午
The path information for images is outlined in the /configuration method.
Cheers.