Did anyone get permission to use the Beatport API yet?

[Kim]

Hi,

I developed a Joomla module using the Beatport API almost two years ago. After I updated it to work with the new API and oAuth Beatport changed their policy to make the API only available for approved partners. Now the websites using my module can not promote their Beatport releases any more and development on the module has grinded to a halt.

I requested permission on 22 September but got no reply. Has anyone got permission or a reply to their request?

I need to know what to tell the website administrators using my module.

Thanks.

[Jensvan]

the same here, no reply

[Ollie Brooke]

Same here - try the Juno API until beatport make a decision?

--
You received this message because you are subscribed to the Google Groups "Beatport API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beatport-api...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jay Epoch]

Nope! Still no permission.

-Jason@Proton

[Ollie Brooke]

I wonder why? Seems like it's not a coincidence that beatport just got sold...

--

[Antoine Lorence]

Same for me. I asked on september 17 to understand the error message I just started to get (The API Client for Key XXX has been deactivated). They answered on sept 22 to announe they will answer within 14 business day. In the same time, I sent a more detailed mail on sept 19 to ask for a valid key, explicating how the soft I develop work and how it uses the API. They never answered at this one.

[Adau]

You can still use the old version of the API for non oAuth requests, but there is no more documention.

Le samedi 5 octobre 2013 13:00:06 UTC+2, Kim a écrit :

[Antoine Lorence]

Do you have examples Adau ? The quick tests I just did show me that simple requests are still rejected by Beatport server: http://api.beatport.com/catalog/3/search?query=beyer

{"metadata":{"error":"Access Denied","message":"Invalid timestamp\/nonce combination","request":{}},"results":[]}

Or the address for the old API has changed ? Maybe some old API parts are accessible without OAuth, but can you tell us which one ?

Antoine

[Adau]

You can use the old API using the v=2.0 parameter:
http://api.beatport.com/catalog/search?v=2.0&format=json&query=Beyer

[Antoine Lorence]

Okay, thank you very much. I didn't know this tips, it could be really useful.

[Ollie Brooke]

Wow! That could be awesome!

--

[Ollie Brooke]

It doesn't seem to work for all API calls.  I got my type-ahead widget working but when I try to load all tracks by an artist or label I get an authoris(z)ation error;

file_get_contents(http://api.beatport.com/catalog/3/tracks?v=2.0&facets[]=performerName:Ollie+Brooke&sortBy=publishDate%20desc&perPage=1): failed to open stream: HTTP request failed! HTTP/1.1 401 Authorization Required

[Greg Skowronski]

Something like this does work though...

http://api.beatport.com/catalog/search?v=2.0&format=json&query=genreId%3A12&publishDateStart=2013-10-08&publishDateEnd=2013-10-08

[Ollie Brooke]

Hmm, so merely reconfiguring our requests can actually retrieve the data we need it would seem.

Instead of having to specify label or artist we can just run a query for that entity and retrieve the same data as before?

Can someone from Beatport comment on this?  Specifically, is this something you'll continue to make available or is there a move to reduce the level of public access to the API and this is just a loophole that will be closed soon?

Thanks a lot for finding and sharing this Greg!  Can we check out your app/site that's using the API?

On Wed, Oct 9, 2013 at 7:42 AM, Greg Skowronski <gr3...@gmail.com> wrote:

Something like this does work though...

http://api.beatport.com/catalog/search?v=2.0&format=json&query=genreId%3A12&publishDateStart=2013-10-08&publishDateEnd=2013-10-08

--

[Adau]

You don't have to reconfigure your requests, simply change the API version. Here's your previous request using 1.0 version:
http://api.beatport.com/catalog/tracks?v=1.0&facets[]=performerName:Ollie+Brooke&sortBy=publishDate%20desc&perPage=1
Note that you have to remove the "/3/" from the URL (corresponding to the 3.0 version).

I don't know how much longer the old API will be available, but it works for this moment.

[Greg Skowronski]

Ollie

It's a windows app and yea I was meaning to post the source code to BitBucket but too busy! I'll see what I can do.

I have no idea what Beatport are trying to achieve by locking access to their API but I hope it works out for them. For devs it has been nothing but a pain in the ar5e so far.

[Stone]

Hi all, 

I've been using the Beatport API for some time now. I have an application that helps labels organize data and also to generate urls to help promote their beatport releases.

Unfortunately, Beatport has turned down my api request as I have a login system on my site and I am a business. It's unfortunate (for Beatport and my users) that I won't be able to easily drive traffic towards the Beatport site now. As this was my only intention. To generate links for artists to use for promotional purposes.

That all being said, it would have been nice to have spoken to someone at Beatport or received something other than a boiler plate rejection letter. My service in no way competes with them - only complements. And now everyone loses out. 

Why offer an API if another business can't use it? I'd love for someone on the Beatport staff to share their reasoning behind that decision.

Maybe it's for the best though. Seems like things are changing for Beatport lately and not necessarily for the best. This just kind of cements that for me. 

So - If you guys are hoping to use the API for anything business oriented in any way or have a login on your site don't bother applying, your request won't be accepted. 

Best of luck to everyone. 

-Stone

On Saturday, October 5, 2013 4:00:06 AM UTC-7, Kim wrote:

[Ollie Brooke]

I got the same email this morning :(

Seems an odd tactic - I wonder if they'll keep the old API versions open?

--

[Kim]

I also got a refusal. I asked 10eur for updates and support for a year. Apparently this is seen as commercial use. Lucky I didn't plan on making a living out of that, I would have been bankrupt within a month. When I just developed my module I have been in contact with Beatports legal office. They assured my script was ok for Beatport and that Beatport applauded my efforts. Apparently times have changed and they don't need promotion on Joomla sites any more.

[Antoine Lorence]

Same for me. My application seems to be considered as Commercial. It's a bit funny when you know this is an open source project, hosted on Github, totally free of charge. I also don't have member accounts on the website or in the application. I don't get money for this personal work... But Beatport decided to break 13 months of development like that...

[Mateo Murphy]

I'm not sure if this is new, but there's a section in beatport's terms and conditions regarding the API: https://knowledgebase.beatport.com/kb/article/000115#apiterms

Amongst other things, it states:
"The Beatport API may only be used with those platforms from which a functional link is made available that, when accessed, takes the user to the page on Beatport's website where the user can access the associated content. You may not utilize the Beatport API in a manner that does not permit successful linking to, redirection to or delivery of the applicable Beatport web page. "

I imagine this is the reason behind many of the rejections, and Beatport is probably sending a generic response that mentions commercial use even when this isn't strictly the case.

Kim, regarding your joomla module; you might be able to recode it so that the labels who want to use it furnish their own API Key. I believe that would conform to the terms and conditions, but only Beatport would be able to say for sure.

It would certainly be nice for them to chime in here…

[Stone]

Seems like nobody here is making any real money with their apps or use cases. Frankly, it's really unprofessional for this forum not to have somebody from Beatport chiming in once in a while.

Maybe we should take our apps (and our music buying practices) somewhere else. 

This makes me feel really bad about putting so much work into running a label and supporting Beatport as a store.

It's also good food for thought too...

[Stone]

FYI, I've kindly emailed Beatport and asked for their reasoning. I urge everyone else to as well. Maybe if enough of us inquire, they'll reconsider their terms.

[Greg Skowronski]

This whole Beatport API deserves one big LOL

Get this....

I work for one of the top DJs in the world (as per DJ Mag voting thing how legit that is is another matter!). All my app does is downloads track previews so I can listen to them off line on my phone etc. I send a few to him and if he likes them he plays those tracks on his radio show and podcast. He clearly lists all the tracks he plays on his website, has his top 10 chart on Beatport as well...and even mentions you can buy those tracks on Beatport.

Great promotion for Beatport yes? NO! Beatport seem to think my app is commercial even though I am the only person who uses it.

LOL

Well done Beatport, well done.

Like I said I hope it works out for you. 

No hard feelings.

[Timur Asaliev]

Hey Greg, if all you want is previews you can still do that with using API v1. 

For example, latest track from Anjunadeep: http://api.beatport.com/catalog/tracks?v=1.0&format=json&facets[]=labelName:Anjunadeep&perPage=1&sortBy=publishDate+desc

In the resulting JSON object we can see the sample url: $object->results[0]->sampleUrl. Rest is easy, just download the sample or stream it via wifi/3g.

I'm using a similar approach to display track previews on a friendly label's site.

[Timothy Appnel]

I agree. This is a pain and seems counter productive. Does anyone have the version 1 API docs? Seems Beatport really doesn't want us to use their API and took the docs down.

[Kim De Vylder]

Hi Mateo, thanks for your advice. I already did recode the module so users could use their own API key and published the update right before Beatport turned everything off. I followed the style guidelines for use of their icons and every item had direct links to the Beatport pages for purchase. The problem is I don't have a working API key myself so it's very difficult to keep developing the module. Also if it's this difficult to get an API key for anyone it's no use for me to keep spending my time on development. The market for my module was already very niche. Only labels/artists with a Joomla site were able to use it. This has been trimmed down to only labels and artists with a Joomla site who have an API key. I haven't found one yet ;-)

Its sad to see all the work going down the drain but if Beatport doesn't want the extra promotion I'm not going to be the one begging them to allow me to help them promoting their releases. After all it was free and effortless promotion for them. In my reality they should have been thankfull

2013/10/16 Mateo Murphy <mateo....@gmail.com>

[will banks]

jesus christ I have been working on trying to get some kind of data from the Beatport API for 2 days now. I've tried everything.
I am using the OAuthSimple.php class which seems pretty simple to understand.
I have read through the OAuth 1.0 documentation and as far as I can see you just need to open a URL like this:

file_get_contents(https://oauth-api.beatport.com/catalog/3/releases?facets=genreName%253APsy-Trance&oauth_consumer_key=510c32d75138a1724257e8fbcf9392477449807b&oauth_nonce=0TZil&oauth_signature=YUthYNb4uHwGaKF1kUCO9OiOHKU%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1396759658&oauth_token=8e364dc5e46243c546756460d350fec831236367&oauth_version=1.0&page=1&password=xxxx&username=xxxx)

( tried adding my beatport username and password in there too to see if that works. but I just get:

failed to open stream: HTTP request failed! HTTP/1.1 401 Authorization Required

WHAT AUTHORIZATION??

I've already given the god damn token, key etc? What more authorization does it need?

This is totally doing my head in.

Somebody please help

[Federico Giust]

Hi Will,

The problem with your code is that you are trying to use file_get_contents.

For it to work with the new API you need to install first the PHP OAuth extension on your server (http://php.net/manual/en/book.oauth.php).

Once this is installed, you need to use that extension to first make a request to the server to get the token. Once you've done that I think is better to use cURL to make the final request to the server.

Have a look at this code 

https://github.com/fedegiust/Beatport-API-JSON-feed (It is based on Beatport OAuth Connect by Tim Brandwijk)

This is already working on my server, and it even logs all API calls to my DB. 

This is also used as a middle server by my wordpress plugin (http://wordpress.org/plugins/beatport-discography-shortcode/)

Hope it helps.

Federico

[Federico Giust]

Another thing, it wont work from localhost. Their API is per domain, so if they given your server access to the api, the calls will only work from your web server where your domain is hosted and not from localhost.

El sábado, 5 de abril de 2014 20:58:48 UTC-3, will banks escribió:

[Ashton Hylton]

Did anyone get a response from Beatport about this subject. I'm really interested to hear how people are using the API currently, and how it can be used commercially/non-commercially.

I emailed them asking them to outline what is classed as commercial use, still waiting for their reply.

Thanks

Ashton

[Marten Middeldorp]

Ashton, did you get a reply from Beatport? I'm looking into using the API privately but find it hard to find out how to get started.

Marten