Groups
Conversations
All groups and messages
Send feedback to Google
Help
Training
Sign in
Groups
jamendo-dev
Conversations
About
Problems with tracks API
59 views
Skip to first unread message
Carlo Zanotto
unread,
Jun 22, 2021, 10:41:45 AM
6/22/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jamendo-dev
Hi, there is a problem with the track api,
https://api.jamendo.com/v3.0/tracks?client_id=MYCLIENTID&fuzzytags=rock&include=musicinfo
https://api.jamendo.com/v3.0/tracks?client_id=MYCLIENTID&tags=rock&include=musicinfo
https://api.jamendo.com/v3.0/tracks?client_id=MYCLIENTID&fuzzytags=blues&include=musicinfo
https://api.jamendo.com/v3.0/tracks?client_id=MYCLIENTID&tags=blues&include=musicinfo
The first one returns 10 songs, the second one returns 0 songs.
The third one returns 0 songs, the second one returns the whole 10.
Why is this so? Shouldn't Tags and VarTags be the same thing if there is only one tag?
Carlo Zanotto
unread,
Jun 22, 2021, 10:47:32 AM
6/22/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jamendo-dev
This happened after jamendo returned a 500 error for a couple of minutes.
Carlo Zanotto
unread,
Jun 22, 2021, 11:29:36 AM
6/22/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jamendo-dev
Looks like it's fixed now
Reply all
Reply to author
Forward
0 new messages