Back to store

Dance-Tunes Public API

This page describes the API for Dance-Tunes topic-by-topic. The API serves as an interface between the database and the client front-end. The language used is XML over HTTP. In the near future we will expand the possibilities of this API. You can think of cart/buy functionality, rss feeds, etc.


Request a Dance-Tunes Open API key

Please login before requesting a Dance-Tunes Open API key.

download documentation in PDF

Inspiration

Here are some suggestions


Made with flickr
Create a mashup of the vast photo library of Flickr and Dance-Tunes' extensive music catalogue.

Add previews of tracks to pictures of your favorite DJ's and artists photos on Flickr to hear the sound an artist or DJ represents.


Made with facebook
Create a Facebook widget that shows the hottest Dance-Tunes on your Facebook profile.

Use the Dance-Tunes chart to stay up to date on the best dance music right in your Facebook page. Spice up a fan page by adding a player that plays previews of tracks by your favourite artist.


Made with googlemaps
Create a mashup with Google Maps to show famous DJ's and Artists on the world map and play their tracks.

Get a feel for each countries individual sound by playing local Artists tunes on the map. Which country fits your taste best?

Search

Searches tunes, mixes and albums for <string>, which must occur in the album title, tune title, version, artist or label. Also from and till can be used for pagination. <order> indicates if the results should be sorted by: artist, date, genre or title. <sort> indicates whether the results should be sorted in ascending (asc) or descending (desc) order. <ind_tune>, <ind_mix>, <ind_album> indicate what information should be searched. The value of the indicators is Y or N. The search can be limited by using the <field> tag. Possible values are 'artist', 'title', 'version' or 'label'. If the <field> tag is empty the search will use all mentioned fields. The result is a sorted list of tunes, mixes and albums. This are formatted in the same way as the results returned by get_tune_info and get_album_info. Searches are logged. In order to avoid performance issues, the length of the string to search for must be at least two characters.

In 
<cmd>search</cmd>
<session>H0RPJ3HJBVEEOF93XZKU</session>
<string>Tiesto</string>
<from>1</from>
<till>10</till>
<order>artiest</order>
<sort>asc</sort>   
<ind_tune>y</ind_tune>   
<ind_mix>y</ind_mix>   
<ind_album>y</ind_album>
<field>artist</field>
Out 
<?xml version="1.0" encoding="UTF-8"?> 
<reply>
<search_info>
   <total_count>125</total_count> 
</search_info>
<searchresult>
   <tune>
      <rownumber>1</rownumber> 
   See: get_tune_info
   </tune>
   <tune>
      <rownumber>2</rownumber> 
      See: get_tune_info
   </tune>

   <album>
      <rownumber>10</rownumber> 
      See: get_album_info
   </album>
   <album>
      <rownumber>11</rownumber> 
      See: get_album_info
   </album>

</search_result>
<security>
   <session>H0RPJ3HJBVEEOF93XZKU</session>
</security>
</reply>