You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
None (application is not using authentication i.e., implicit flow)
I noticed that this endpoint is marked as deprecated in the SoundCloud API docs above. This endpoint is useful to perform a quick check to see if a user is already following another user. This is useful for providing a visual indication on 3rd party integrations if a user follows another user.
If this endpoint is removed, then this check can only be performed by paging through all of a users followings, and searching to see if the other user id is present in the collection. This collection could be up to 2000 users, and therefore require 10 API calls in order to perform this check.
As it stands, a very lightweight check can be done as this method actually issues a HTTP 303 (Redirect Method) to the /users/{id} endpoint meaning no data even needs to be requested from the API.
Can I request that this method is not deprecated?
The text was updated successfully, but these errors were encountered:
Title: Deprecated API warning - /users/{id}/followings/{id}
Endpoint(s):
GET /users/{id}/followings/{id}
https://developers.soundcloud.com/docs/api/explorer/open-api#/users/get_users__user_id__followings__following_id_
Scope(s):
I noticed that this endpoint is marked as deprecated in the SoundCloud API docs above. This endpoint is useful to perform a quick check to see if a user is already following another user. This is useful for providing a visual indication on 3rd party integrations if a user follows another user.
If this endpoint is removed, then this check can only be performed by paging through all of a users followings, and searching to see if the other user id is present in the collection. This collection could be up to 2000 users, and therefore require 10 API calls in order to perform this check.
As it stands, a very lightweight check can be done as this method actually issues a HTTP 303 (Redirect Method) to the /users/{id} endpoint meaning no data even needs to be requested from the API.
Can I request that this method is not deprecated?
The text was updated successfully, but these errors were encountered: