Difference between revisions of "YTMND:API"

From YTMND
Jump to: navigation, search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== YTMND Developer API ==
 
== YTMND Developer API ==
  
The YTMND Developer API or Developer Interface is a method of gathering information from YTMND for use in external applications. In its current form the API allows limited access to YTMND data via a standard [http://en.wikipedia.org/wiki/REST REST] interface and offers several [[YTMND:API:Response Formats|response formats]]: [[w:XML|XML]], [[w:JSON|JSON]], [[w:JavaScript|JavaScript]], and [http://www.php.net/manual/en/function.unserialize.php serialized PHP]. In the future further data will most likely be available from this API. Currently there are no prerequisites to use the API, it is available to all for free, no YTMND account is currently required.
+
The YTMND Developer API or Developer Interface is a method of gathering information from YTMND for use in external applications. In its current form the API allows limited access to YTMND data via a standard [http://en.wikipedia.org/wiki/REST REST] interface and offers several [[YTMND:API:Response Formats|response formats]]: [[w:XML|XML]], [http://json.org/ JSON], [[w:JavaScript|JavaScript]], [http://www.php.net/manual/en/function.unserialize.php serialized PHP] and [http://yaml.org YAML]. In the future further data will most likely be available from this API. Currently there are no prerequisites to use the API, it is available to all for free, no YTMND account is currently required.
  
 +
The API was created to allow technical users to create feature for use both on and off the site. The aim of the API is to provide maximum flexibility while having a fairly static data format. In many places, the API provides more data than is visibly available on the actual site itself. This was done in the hope that it would entice more developers to play with the API as well as the fact that a lot of data is not pertinent to every day viewing (also, max is lazy).
  
If you have worked with the [http://apidoc.digg.com/ Digg API] this documentation should be fairly similar as the YTMND API was modeled in a large part on the [http://www.digg.com Digg] API. This was done because it is a straight forward and useful implementation. It is possible that in the future the interface will change, but changes will hopefully be mentioned in the documentation.
 
  
  
 
*[[YTMND:API:Basic Overview|Basic Overview]]
 
*[[YTMND:API:Basic Overview|Basic Overview]]
 +
*[[YTMND:API:Application Requests|Application Requests and Discussion]]
 +
*[[YTMND:API:Examples|Examples]]<br><br>
 
*[[YTMND:API:Response Formats|Response Formats]]
 
*[[YTMND:API:Response Formats|Response Formats]]
 
*[[YTMND:API:Methods|API Methods and Limitations]]
 
*[[YTMND:API:Methods|API Methods and Limitations]]
:*[[YTMND:API:Methods:Users|Users]]
+
*[[YTMND:API:Interfaces|Interfaces]]
:*[[YTMND:API:Methods:Sites|Sites]]
+
:*[[YTMND:API:Interfaces#Sites|Sites]]
*[[YTMND:API:Examples|Examples]]
+
:*[[YTMND:API:Interfaces#Users|Users]]
 +
*[[YTMND:API:Error Codes|Error Codes]]<br><br>
 +
*[[YTMND:API:Roadmap|The API Roadmap]]
 +
*[[YTMND:API:Authentication and Remote Data Storage|Authentication and Remote Data Storage]]
 +
*[[YTMND:API:Contest|API Contest]]

Latest revision as of 11:04, November 5, 2007

YTMND Developer API

The YTMND Developer API or Developer Interface is a method of gathering information from YTMND for use in external applications. In its current form the API allows limited access to YTMND data via a standard REST interface and offers several response formats: XML, JSON, JavaScript, serialized PHP and YAML. In the future further data will most likely be available from this API. Currently there are no prerequisites to use the API, it is available to all for free, no YTMND account is currently required.

The API was created to allow technical users to create feature for use both on and off the site. The aim of the API is to provide maximum flexibility while having a fairly static data format. In many places, the API provides more data than is visibly available on the actual site itself. This was done in the hope that it would entice more developers to play with the API as well as the fact that a lot of data is not pertinent to every day viewing (also, max is lazy).