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 ?
Antwoord deur Travis Bell
op 15 Mei 2013 om 9:22 VM
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.
Antwoord deur joshuahotw
op 24 September 2013 om 1:09 VM
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.
Antwoord deur Travis Bell
op 24 September 2013 om 10:14 VM
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.
Antwoord deur joshuahotw
op 24 September 2013 om 11:29 VM
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
Antwoord deur Travis Bell
op 24 September 2013 om 11:45 VM
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.
Antwoord deur joshuahotw
op 24 September 2013 om 12:23 NM
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
Antwoord deur Travis Bell
op 24 September 2013 om 12:46 NM
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.
Antwoord deur joshuahotw
op 24 September 2013 om 12:49 NM
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
Antwoord deur Travis Bell
op 24 September 2013 om 12:51 NM
Cool. Indeed, typo!
No, v3 is JSON only.
Cheers.
Antwoord deur joshuahotw
op 29 September 2013 om 2:50 NM
Travis, for the image link, what is the server info for them ? Thanks a lot for your input.
Antwoord deur Travis Bell
op 29 September 2013 om 3:54 NM
The path information for images is outlined in the /configuration method.
Cheers.