The Movie Database-ondersteuning
Ondersteuning → API-ondersteuning
Api not working
geplaatst door perthiSTAFFMOD op 9 augustus 2015 om 11:13 AM
When using KODI I get the following message when I try to fetch data from the movie databse (I tried many different movies, searches etc... ). The error message is always the same.
{"status_code":34,"status_message":"The resource you requested could not be found."}
I think its nothing to do with KODI because, I get the same message when using CURL directly from the command line, for instance if I try to get info about the film "Valkyrie" i type the following.
curl -o output.txt http://api.tmdb.org/3/search/movie?api_key=57983e31f*******************************&query=Valkyrie&year=2008&language=en
I dont think its a problem with the key, because I tried to use a wrong key, and then I get an error message about the key instead.
Reactie van Dale
op 11 augustus 2015 om 2:43 PM
The URL works with my own Key, might be that KODI are not handling the status code 34. I ran into a similar issue with my own app, something changed and things started returning status code 34. I found putting a retry into my app and the resource came back.
Reactie van perthi
op 11 augustus 2015 om 4:14 PM
Yes, but the problem is the same also when I use CURL on the command line. Seems that actually, the resource is not available.
Reactie van Travis Bell
op 12 augustus 2015 om 10:02 AM
Hi perthi,
This call seems to be working fine for me (with your API key, I've truncated it for privacy reasons):
Are you sure you're entering your API key correctly? The key you posted above is 5798... when the one I see in your account is 8aa7d...
Reactie van perthi
op 12 augustus 2015 om 1:18 PM
Hi again, thanks for helping out. The problem is not the keys, I have two keys, one came with Kodi, and the otherone I aplied for exactly in order to debug this problem. I addition I also get another error messageabout invalid key if I purposely enter an incorrect key,.. so I think e can exclude the keys as the source of the problem.
Below is the output I get if I enter excactly the same command as you show above.
perthi@perthi-mint:~ > curl -v https://api.tmdb.org/3/search/movie/?api_key=57********************************************&query=Valkyrie&year=2008&language=en [1] 13600 [2] 13601 [3] 13602 perthi@perthi-mint:~ > * Hostname was NOT found in DNS cache * Trying 198.41.186.159... * Connected to api.tmdb.org (198.41.186.159) port 443 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server key exchange (12): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using ECDHE-RSA-AES128-GCM-SHA256 * Server certificate: * subject: C=US; ST=CA; L=San Francisco; O=CloudFlare, Inc.; CN=ssl4779.cloudflare.com * start date: 2014-11-19 14:42:46 GMT * expire date: 2015-10-16 07:24:56 GMT * subjectAltName: api.tmdb.org matched * issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign Organization Validation CA - G2 * SSL certificate verify ok. > GET /3/search/movie/?api_key=57****************************************** HTTP/1.1 > User-Agent: curl/7.35.0 > Host: api.tmdb.org > Accept: */* > < HTTP/1.1 404 Not Found * Server cloudflare-nginx is not blacklisted < Server: cloudflare-nginx < Date: Wed, 12 Aug 2015 17:18:07 GMT < Content-Type: application/json;charset=utf-8 < Content-Length: 84 < Connection: keep-alive < Set-Cookie: __cfduid=dd3985f255e531de3f974579bb365feba1439399887; expires=Thu, 11-Aug-16 17:18:07 GMT; path=/; domain=.tmdb.org; HttpOnly < Access-Control-Allow-Origin: * < Cache-Control: public, max-age=36000 < Status: 404 Not Found < X-RateLimit-Limit: 40 < X-RateLimit-Remaining: 38 < X-RateLimit-Reset: 1439397702 < CF-Cache-Status: HIT < CF-RAY: 214dd66f1ca80a48-ARN < * Connection #0 to host api.tmdb.org left intact {"status_code":34,"status_message":"The resource you requested could not be found."}Reactie van Travis Bell
op 12 augustus 2015 om 4:39 PM
Ah, you're getting status 34, for something reason I thought 7, "invalid key".
Remove the trailing slash in your URL:
You have:
See the difference?
Reactie van perthi
op 13 augustus 2015 om 1:46 PM
Yes, I do, I dont know how the / sneaked in, but anyway, I still get the same message. Now U just copy and pase your command just to be sure (I just replace the key)''
curl -v http://api.tmdb.org/3/search/movie?api_key=5798****************************************&query=Valkyrie&year=2008&language=en [4] 4603 [5] 4604 [6] 4605 [1] Exit 127 http://api.tmdb.org/3/search/movie/?api_key= 57983e31fb435df4df77afb854740ea9 [2] Done query=Valkyrie [3] Done year=2008 Hostname was NOT found in DNS cache * Trying 198.41.185.159... * Connected to api.tmdb.org (198.41.185.159) port 80 (#0) > GET /3/search/movie/?api_key=57983e31**************************' HTTP/1.1 > User-Agent: curl/7.35.0 > Host: api.tmdb.org > Accept: */* > < HTTP/1.1 404 Not Found < Date: Thu, 13 Aug 2015 17:44:19 GMT <> < Content-Type: application/json;charset=utf-8 < Content-Length: 84 < Connection: keep-alive < Set-Cookie: __cfduid=d312c929690bc2497297db51261f984f41439487858; expires=Fri, 12-Aug-16 17:44:18 GMT; path=/; domain=.tmdb.org; HttpOnly < Access-Control-Allow-Origin: * < Cache-Control: public, max-age=36000 < Status: 404 Not Found < X-RateLimit-Limit: 40 < X-RateLimit-Remaining: 39 < X-RateLimit-Reset: 1439487869 < CF-Cache-Status: EXPIRED * Server cloudflare-nginx is not blacklisted < Server: cloudflare-nginx < CF-RAY: 21563a2dc5fc05a9-ARN < * Connection #0 to host api.tmdb.org left intact {"status_code":34,"status_message":"The resource you requested could not be found."}Reactie van perthi
op 13 augustus 2015 om 1:52 PM
I think the line
Is important, in you output it says 201 OK
I am able to ping api.tmdb.org, but maybe a firewall/port forwarding issues ? Is it any particular port I need to open (I think the SSL port is set to port forwarding)
Reactie van Travis Bell
op 13 augustus 2015 om 3:04 PM
In your curl command you don't have a trailing slash but you do in the cURL response. Something weird is going on, on your end. I've tried this cURL command on 3 machines and asked 2 friends and we can all access this request.
404 is right if the resource can't be found, which is right with the trailing slash.
Try wrapping your cURL command in single quotes:
travisbell$ curl -v 'http://api.tmdb.org/3/search/movie?api_key=****&query=Valkyrie&year=2008&language=en' * Hostname was NOT found in DNS cache * Trying 198.41.185.159... * Connected to api.tmdb.org (198.41.185.159) port 80 (#0) > GET /3/search/movie?api_key=****&query=Valkyrie&year=2008&language=en HTTP/1.1 > User-Agent: curl/7.37.1 > Host: api.tmdb.org > Accept: */* > < HTTP/1.1 200 OK < Date: Thu, 13 Aug 2015 19:02:14 GMT < Content-Type: application/json;charset=utf-8 < Transfer-Encoding: chunked < Connection: keep-alive < Set-Cookie: __cfduid=d251f6deae67082ebcc976ef48aab98941439492534; expires=Fri, 12-Aug-16 19:02:14 GMT; path=/; domain=.tmdb.org; HttpOnly < Access-Control-Allow-Origin: * < Cache-Control: public, max-age=28800 < ETag: W/"1ed6183c3c260205e0c1ff7e0befff11" < Status: 200 OK < Vary: Accept-Encoding < X-Memc: HIT < X-Memc-Age: 3793 < X-Memc-Expires: 7007 < X-Memc-Key: 9f0d3f1c4a476ec871c75a79d32d38df < X-RateLimit-Limit: 40 < X-RateLimit-Remaining: 38 < X-RateLimit-Reset: 1439492538 < CF-Cache-Status: EXPIRED < Expires: Fri, 14 Aug 2015 03:02:14 GMT * Server cloudflare-nginx is not blacklisted < Server: cloudflare-nginx < CF-RAY: 2156ac5520f31ba9-SEA < * Connection #0 to host api.tmdb.org left intact { "page": 1, "results": [ { "adult": false, "backdrop_path": "/ptNcTh2bewqzcV2qVpjDgsh6pTs.jpg", "genre_ids": [ 18, 36, 53, 10752 ], "id": 2253, "original_language": "en", "original_title": "Valkyrie", "overview": "Wounded in Africa during World War II, Nazi Col. Claus von Stauffenberg returns to his native Germany and joins the Resistance in a daring plan to create a shadow government and assassinate Adolf Hitler. When events unfold so that he becomes a central player, he finds himself tasked with both leading the coup and personally killing the Führer.", "release_date": "2008-12-25", "poster_path": "/54GgkO63zZyJJb5Fk2CKvNIoUvr.jpg", "popularity": 2.070591, "title": "Valkyrie", "video": false, "vote_average": 6.6, "vote_count": 429 }, { "adult": false, "backdrop_path": null, "genre_ids": [], "id": 272231, "original_language": "en", "original_title": "Die Walkure [The Valkyrie]", "overview": "The Valkyrie takes us on theatrical voyage into a world that is in a never ending state of war, whether on the battlefield or in the family. Nobody is willing to let anyone out of their sight. A father kills his son and rejects his daughter. From this tragedy the nightmares and hidden aspirations of human history emerge, ranging from dreams of lost paradise via the apocalypse to the utopian idea that at least the final judgment an individual might be capable of bringing about the world's redemption.", "release_date": "2008-01-01", "poster_path": null, "popularity": 1.000576, "title": "Die Walkure [The Valkyrie]", "video": false, "vote_average": 0.0, "vote_count": 0 }, { "adult": false, "backdrop_path": "/qLhvLfawp8PZKSsyF3We7koOLA6.jpg", "genre_ids": [ 99, 10752 ], "id": 253143, "original_language": "en", "original_title": "Operation Valkyrie: The Stauffenberg Plot to Kill Hitler", "overview": "July, 1944. As WWII raged on, a group of conspirators, led by Claus von Stauffenberg, plotted to assassinate Hitler and end his reign of terror. Using rare color footage, painstakingly recreated dramatizations, detailed CG reconstructions and exclusive interviews with leading historians, this thrilling documentary presents the definitive record of what happened before, during and after these pivotal events.", "release_date": "2008-11-04", "poster_path": "/tRcPLIz3coHppWYLK710WnWiPVT.jpg", "popularity": 1.000715, "title": "Operation Valkyrie: The Stauffenberg Plot to Kill Hitler", "video": false, "vote_average": 0.0, "vote_count": 0 } ], "total_pages": 1, "total_results": 3 }Reactie van perthi
op 13 augustus 2015 om 4:14 PM
YESS!!! That worked, I dont really understand why,
But still, this is when use curl form the command line, when I try update from Kodi the problem is still the same
Reactie van perthi
op 13 augustus 2015 om 4:18 PM
From the kodi log I now get this error (still), the cause is probably the same, but how to fix it ?
Reactie van Travis Bell
op 13 augustus 2015 om 4:34 PM
That looks like a different error, but I am not sure.
"timeout" was reached, and "failed with code 0" sounds like a connection problem. Probably best to post this on the Kodi forums and see what they have to say about it.
Reactie van perthi
op 18 augustus 2015 om 4:27 PM
OK, i will try at the Kodi forum as well, and update you on the result of the inquiry here.