Soporte de The Movie Database
Soporte → Soporte de API
Is the 2.1 API still supported?
publicado por smsithlordSTAFFMOD el 16 de septiembre de 2013 a las 20:30
Having trouble with the database using the old 2.1 API, just want to make sure it hasn't been discontinued or anything.
Contestado por Travis Bell
el 16 de septiembre de 2013 a las 23:55
Hi smsithlord,
No, it was officially retired today. We've sent out numerous notices starting around 4.5 months ago stating that September 15 was when it would be shut down.
V3 is the only supported and available API at this time.
Contestado por smsithlord
el 17 de septiembre de 2013 a las 00:56
Looks like I got a long night ahead of me. :) Thanks for the quick reply.
Contestado por smsithlord
el 17 de septiembre de 2013 a las 16:26
All up to date now. For the the solution was to write a small parser in JavaScript that converted the JSON into Valve's KeyValue's format so my Source engine game could process the data easily. Turned out to be much easier than using TinyXML to parse the 2.1 responses. Thanks again for this awesome service! You get lots of credit in my utility. I'll let you know when I release the big new version, should be this week some time!
Contestado por Travis Bell
el 17 de septiembre de 2013 a las 16:43
You're welcome.
Cool, thanks.
Contestado por Alex_D
el 20 de noviembre de 2013 a las 15:05
Hi smsithlord, Can you share your script which comverts V3 to V2 API?
Contestado por Alex_D
el 7 de diciembre de 2013 a las 04:16
Hi there!
We have application that use API V2. Now application is unable to retrive metadata of the movies. There is no way to update the application. Is there any script for simulation V2 API using V3? Is there any chance that V2 will be supported. Thanks!
Contestado por Travis Bell
el 7 de diciembre de 2013 a las 11:50
Hi Alex_D,
It's doubtful there would be a way to simulate 2.1 responses with v3. The difference in format (XML vs. JSON) and very different responses would make it near impossible.
There is no chance of 2.1 coming back, the infrastructure that it ran on doesn't even exist anymore. 2.1 was just to expensive to support both from an engineering and ops perspective.