Search endpoints response object does not match documentation - next_href contains deprecated "offset" instead of "cursor"

Search endpoints response object does not match documentation - next_href contains deprecated offset instead of cursor

Issue found on: November 22nd, 2021

Endpoint(s):

• GET /tracks?q=b&linked_partitioning=true&limit=10
• GET /playlists?q=b&linked_partitioning=true&limit=10
• GET /users?q=b&linked_partitioning=true&limit=10

Scope(s):

• None (application is not using authentication i.e., implicit flow)

Steps to reproduce:

Call GET on Search endpoints

Expected behaviour:

next_href should have cursor param in query string as defined in example response, see: documentation
e.g. "next_href": "https://api.soundcloud.com/collection?page_size=10&cursor=1234567"

Actual behaviour:

next_href contains deprecated query string param offset
e.g. "next_href": "https://api.soundcloud.com/playlists?limit=10&linked_partitioning=true&offset=10&q=b"

Start by reproducing the behavior on the listed GET /tracks, /playlists, and /users search endpoints with linked_partitioning=true and limit=10. Compare each next_href value with the OpenAPI documentation; done means the response uses the documented cursor query parameter instead of the deprecated offset parameter.