Welcome to the Beatport API Documentation
The Beatport API allows third parties to develop applications using the Beatport catalog. Beatport has begun to transition over to an OAUTH structure, therefore a key is required in order to make API requests. Beatport's process for requesting an API has also changed, requiring a detailed description of the API usage, URL or app name, and if possible information on how Beatport as a brand will be presented to other users for each request.
If you wish to include Beatport logos in your application, please follow the standards outlined in the Beatport Style Guide.
As we continue to improve on the OAUTH experience, below are a few instructions for using the new documentation.
- When your key is generated, you will be automatically provided access to our Catalog information.
- You must enter your API Key and Secret at the top of the page prior to using the documentation.
- You must login to your Beatport account credentials in order to begin using the documentation.
- To access Beatport's API documentation, click here.
For more information on how to use OAUTH 1.0, please go here. http://oauth.net/documentation/spec
Note: Oauth requests contain a nonce value as well as a timestamp. In order to prevent replays of api requests the timestamps need to match our servers as closely as possible. In order to avoid any issues please make sure you are using an NTP server to ensure your requests do not get rejected.
Oauth API endpoints
The endpoints for performing the oauth dance are as follows:
This requests the initial basic oauth basic token, adhering to the standard OAuth implementation.
This is the login url where the user will verify your application and the rights your application is being granted. The html content is designed to accept a beatport.com username and password.
This requests the access token that can be used to call api endpoints. It adheres to the standard OAuth implementation. As with standard OAuth, this requires the verifier parameter.
Direct Access Token
This performs a direct authentication, thereby bypassing the Authorize page and submitting a verify parameter. Instead, this requires a username and password as used with beatport.com. This is useful for obtaining the direct access token immediately in non-web applications. Using this authentication method requires special permissions for your API key.
username (string): The beatport.com username
password (string): The beatport.com password