Getting Started

• Overview
• Methods of Locker Loading

Scenarios

• Locker Load of a single file
• Locker Load using a zip file
• Locker Load using password
  protected zip file
• Locker Load using m3u playlist
  • Minimum playlist
  • Advanced playlist features

Implementation Details

• Obtain Partner Token
• Locker load using HTML/JavaScript
  • Include the JavaScript in your page.
  • Add the locker load links.
• Locker load using MP3tunes API
  • Obtain a session ID
  • lockerLoad API call Parameters
  • lockerLoad sample request
  • lockerLoad sample response

METHODS OF LOCKER LOADING

The locker load functionality is implemented in one of two ways:

• Initiate transfer via HTML/JavaScript - The simpler method of implementation, this method is generally used when presenting the user with the option of downloading purchased tracks or transferring those tracks into an MP3tunes locker.
• Initiate transfer via the [MP3tunes Locker API](http://www.mp3tunes.com/api/) - This can be used to initiate the locker load process automatically, and also contains provisions for automatically creating a locker if one does not already exist.

With each method, it is required that the content to be locker loaded exists on a URL that can be accessed by the MP3tunes servers to load the content into the appropriate locker. The locker load process fetches the content from a provided URL and adds the tracks to the user's locker. The URL may be password protected, as long as the username and password can be transferred in the URL to retrieve the file. Any access control based on user sessions cannot be used in locker loading.

Content may be locker loaded as either single files, a zip file, or an m3u type playlist. Loading as a zip file or an m3u playlist is more desirable than as single files.