Bad url in api request

[j...@linkfire.com]

Hey

This api request:

http://api.7digital.com/1.2/track/search?oauth_consumer_key=<key>&pageSize=50&q=SEUM71400257

returns as the first response, a track with a bad url:

http://www.7digital.com/artist/tove-lo-hippie-sabotage/release/truth-serum/?h=06

should have been:

https://www.7digital.com/artist/tove-lo/release/truth-serum/?h=06

I guess it is a problem that occurs when you combine artists as you do.

Do you have any suggestions for a workaround?

Best

Jannik Jepsen

Linkfire

[Daniel]

Hi Jannik,
This is a known issue when the artist for a track differs from the artist in the containing release. We should deploy by the end of next week. In the mean time you can look at the url in release/url instead of url under the track element. It will link you to the correct release but without highlighting the requested track.

This email, including attachments, is private and confidential. If you have received this email in error please notify the sender and delete it from your system. Emails are not secure and may contain viruses. No liability can be accepted for viruses that might be transferred by this email or any attachment. Any unauthorised copying of this message or unauthorised distribution and publication of the information contained herein are prohibited.

7digital Limited. Registered office: 69 Wilson Street, London EC2A 2BB.
Registered in England and Wales. Registered No. 04843573.

[j...@linkfire.com]

Ok.. as long as you plan to fix it, then i won't have to make special cases for these situations.

Best Jannik

[Daniel]

Hi Jannik,

We have applied a fix. Track urls should always be correct now.