beets
beets copied to clipboard
beetbox
beatport: Switch to Beatport API version 4
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.
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.
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.
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/
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.
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.
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.
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.
Hey, I have found a workaround and opened a PR with the plugin refactor and more detailed information: https://github.com/beetbox/beets/pull/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
