Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

beatport: Switch to Beatport API version 4 #3862

Open
snowyoneill opened this issue Feb 26, 2021 · 12 comments
Open

beatport: Switch to Beatport API version 4 #3862

snowyoneill opened this issue Feb 26, 2021 · 12 comments
Labels
feature features we would like to implement

Comments

@snowyoneill
Copy link

Problem

Looks like the current beatport plug uses the version 3 of the API which has now been retired, so connections are timing out.

beatport: API Error: Error connecting to Beatport API: HTTPSConnectionPool(host='oauth-api.beatport.com', port=443): Max retries exceeded with url:

https://groups.google.com/g/beatport-api/c/HOPkV6acnkI

V4 is now the current: https://api.beatport.com/v4/docs/

I'll get started updating the plugin to match the new spec.

@sampsyo sampsyo added the feature features we would like to implement label Feb 26, 2021
@sampsyo sampsyo changed the title Beatport v3 API deprecated beatport: Switch to Beatport API version 4 Feb 26, 2021
@sampsyo
Copy link
Member

sampsyo commented Feb 26, 2021

Thanks for pointing that out! And for looking into it. 🎧 ✨

@sampsyo sampsyo closed this as completed Feb 26, 2021
@sampsyo sampsyo reopened this Feb 26, 2021
@snowyoneill
Copy link
Author

snowyoneill commented Mar 8, 2021

Not sure if Beatport is going to give me access to their API - I applied over a week ago and i haven't heard back from them yet.

@TiceWise
Copy link

TiceWise commented Mar 22, 2021

I've also requested Beatport API access for a personal project and didn't get a response, so I made a request at the general support page and i got this reply;

Mar 18, 2021:
Hi there,

At this time our Technology Teams are unable to provide API access until our stabilisation period is over, likely another 2 months.

I apologise for the inconvenience.

@TiceWise
Copy link

I've also requested Beatport API access for a personal project and didn't get a response, so I made a request at the general support page and i got this reply;

Mar 18, 2021:
Hi there,

At this time our Technology Teams are unable to provide API access until our stabilisation period is over, likely another 2 months.

I apologise for the inconvenience.

FYI, I replied with the question if the key will be automatically send after 2 months, or if I need to apply again, below their response. So be sure to request access again in 2 months. Since beets was using the V3 API and didn't get V4 access credentials yet, I do wonder who did get access to V4 to 'test' it. (And why they drop an older version while not providing access to a newer version.)

Mar 23, 2021:
Hello,

Thank you for being patient. Our new API is still being worked on. Unfortunately you will have to wait most likely another 2 months, then I suggest request a new key though the link again: https://api.beatport.com/v4/docs/

@awesomer
Copy link
Contributor

awesomer commented Jun 4, 2021

FTR, this is exactly the sort of (not super external developer-friendly) upgrade process that happened when Beatport moved from V2 to V3 of their API. In that case, it unfortunately took them a lot longer than 2 months (a year?) to start granting new API keys.

@TiceWise
Copy link

TiceWise commented Jun 9, 2021

FTR, this is exactly the sort of (not super external developer-friendly) upgrade process that happened when Beatport moved from V2 to V3 of their API. In that case, it unfortunately took them a lot longer than 2 months (a year?) to start granting new API keys.

I'm afraid we're looking at such a period again, i got this reply to my recent request (for my personal project):

Jun 8, 2021, 16:45 MDT:
Hello again,

Unfortunately, our Technology Teams will not be issuing any new API keys in the near future.

Unfortunately, there are no immediate plans for an open API or keyed access. I apologize for the inconvenience.

Sorry you were told you would have to wait 2 months, sorry this has changed and no API keys will be issued at this time.

Please feel free to check back with us later this year.

@df-a
Copy link

df-a commented Feb 3, 2022

It seems v4 is now live and requests for access can be made

https://api.beatport.com/v4/docs/

Once you are in you can request API access, it will redirect you to a beatport.atlassian.net site. I haven't tried it yet myself but it seems to be live.

@alicezou
Copy link
Contributor

Hi, can I work on this?

@sampsyo
Copy link
Member

sampsyo commented Mar 22, 2022

Sounds great, if you're interested!

@alicezou
Copy link
Contributor

alicezou commented Apr 9, 2022

It has been half a month since I submitted the request to Beatport via beatport.atlassian.net. They have not respond to me yet. Does anyone know whether they still give out permission?

Update: it has been a month now. I still get nothing back.

@eejd
Copy link

eejd commented Aug 4, 2022

Any word on the Beatport API work?

@Samik081
Copy link

Samik081 commented Sep 8, 2022

Hey,
I have found a workaround and opened a PR with the plugin refactor and more detailed information: #4477
I have also created the external plugin, so you can already use it. So far, everything works for me ^^ https://github.com/Samik081/beets-beatport4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature features we would like to implement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants