SoundCloud的“解决” API端点返回另一首歌曲 [英] SoundCloud's "resolve" API endpoint returns another song

查看:217
本文介绍了SoundCloud的“解决” API端点返回另一首歌曲的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这很奇怪,但是我在SoundCloud的API的解析端点发现了这个错误。我想解决这个问题:





如果我尝试这种GET:

302 .json?client_id = CLIENT_IDrel =nofollow noreferrer> https://api.soundcloud.com/tracks/4459232.json?client_id=CLIENT_ID



<但这不是所要求的轨道。这是另一个: https://soundcloud.com/other-songs/sunroof



如果我试试这个GET: https://api.soundcloud.com/tracks/320689319.json?client_id=CLIENT_ID 它会返回正确的曲目。



出现问题这个轨道?

解决方案

看起来这是SoundCloud API的问题,现在已经解决了。


This is weird but I found out this error in the resolve endpoint of SoundCloud's API. I want to resolve this track:

If I try this GET: https://api.soundcloud.com/resolve.json?url=https://soundcloud.com/wearecourtship/sunroof&client_id=CLIENT_ID it gives me a 302 with a redirect on this response:

https://api.soundcloud.com/tracks/4459232.json?client_id=CLIENT_ID

But this is not the requested track. This is another one: https://soundcloud.com/other-songs/sunroof

If I try this GET instead: https://api.soundcloud.com/tracks/320689319.json?client_id=CLIENT_ID it returns the correct track.

What goes wrong on this track?

解决方案

It looks like this was an issue with the SoundCloud API, which has now been resolved.

这篇关于SoundCloud的“解决” API端点返回另一首歌曲的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆