Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Plan
Premium
Country
Japan
Issue
The following tracks look exactly the same, but have different IDs.
A: https://open.spotify.com/track/7MuOSVDTgILDaWQmR4iLWo?si=c6b7bae2220c4a8a
B: https://open.spotify.com/track/6sbugnLYosR8vG77QvmKZ5?si=f1ed7a238f56434a
If you get the ID of each track from `GET v1/tracks/{id}`, it returns the correct ID
(A: 7MuOSVDTgILDaWQmR4iLWo, B: 6sbugnLYosR8vG77QvmKZ5)
However, as shown in the following table, when you get recently played track from `GET v1/me/player/recently-played`, track B returns the ID of track A.
v1/tracks/{id} | v1/me/player/recently-played | |
A | 7MuOSVDTgILDaWQmR4iLWo | 7MuOSVDTgILDaWQmR4iLWo |
B | 6sbugnLYosR8vG77QvmKZ5 | 7MuOSVDTgILDaWQmR4iLWo |
I don't know if this is a specification or not, but I'm having trouble collecting data because it's treated as a different track.