spotify2tidal
spotify2tidal moves playlists, favorite albums and tracks and following artists from a Spotify account to a Tidal account. It combines spotipy and tidalapi to do so.
Installation
To install, run
pip install spotify2tidal
Spotify API credentials
Spotify's API requires a registered client with a client ID, client secret and a redirection URI (see client credential flow for more information). To obtain all three of them, head over to the Spotify developer dashboard and create a new app. This will generate both ID and secret for you. To use a redirection link in the application, you need to first whitelist it for your client. On the app settings add one to 'Redirect URIs'. If unsure, simply use https://localhost.
Spotify 'Discover Weekly' playlist ID
In case you intend to also use your 'Discover Weekly' playlist, you need to obtain the corresponding ID for it. This is necessary because this particular playlist isn't exposed like the rest of you playlist through the API. To get the ID, simply go to your 'Discover Weekly' playlist, click on the three dots -> Share -> Copy Link. The ID you are looking for is then between "https://open.spotify.com/user/spotify/playlist/" and "?si=".
Usage
After obtaining all credentials, transferring content is rather simple.
from spotify2tidal import Spotify2Tidal
st = Spotify2Tidal(
tidal_username="name",
tidal_password="pwd",
spotify_client_id="id",
spotify_client_secret="sec",
spotify_redirect_uri="uri",
spotify_discover_weekly_id="weekly",
)
st.copy_discover_weekly()
More examples can be found in the examples directory.
Metadata
Release files for spotify2tidal 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| spotify2tidal-1.1.tar.gz | 19.8 kB | Without provenance | Details for spotify2tidal-1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| spotify2tidal-1.1-py3-none-any.whl | Python 3 | none | any | Details for spotify2tidal-1.1-py3-none-any.whl |
Total release size: 39.5 kB
Release files / spotify2tidal-1.1.tar.gz
| Download URL | spotify2tidal-1.1.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c9af8298ec3e8d2655b5427c000a198cfe1058ac1d5e1a04b9839ee788f5f78e
|
|
BLAKE2b-256 checksum How to use checksums |
5362dcfe15e11647c0166aaaf822347b24a9f2e113f8c3900e0aa041d02b7ed8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Release files / spotify2tidal-1.1-py3-none-any.whl
| Download URL | spotify2tidal-1.1-py3-none-any.whl |
|---|---|
| Size | 19.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5775ff804de7499e9086afba4c791e3f842a52b35c4d179311d8b5ce5c149f38
|
|
BLAKE2b-256 checksum How to use checksums |
f16f4e6cc4220e823c705ef7e5e76161d3216673774109da9c2a1250a5c4345f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Security for spotify2tidal 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.