Difference between revisions of "YTMND:API"
(initial formatting) |
(→YTMND Developer API) |
||
Line 2: | Line 2: | ||
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. 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. 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. | ||
+ | |||
+ | |||
+ | 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. | ||
Revision as of 21:20, June 20, 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. 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.
If you have worked with the Digg API this documentation should be fairly similar as the YTMND API was modeled in a large part on the 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.