soundcloud / soundcloud/api

Is purchase_title officially supported?

Open
#237 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
254
Forks
53
PR merge metrics
No merged PRs in 30d

Description

I'd like users to be able to update the Buy URL as well as the Buy Title for each track. As I'm working on the functionality, I'm finding some inconsistencies. It seems that the option to update a track's Buy Title is limited to certain accounts (possibly paid ones). Even on SoundCloud.com.

SoundCloud Next User - Updating does not work for this users

  • PUT purchase_url does not cause an error
  • PUT purchase_title does not cause an error
  • GET users/{id}/tracks/{track_id} return contains updated purchase_url, but null purchase_title

SoundCloud Next Pro User - Updating works for this users

  • PUT purchase_url does not cause an error
  • PUT purchase_title does not cause an error
  • GET users{id}tracks/{track_id} return contains updated purchase_title and purchase_url

This also seems to be the case on SoundCloud.com metadata editor. See screenshots below.

Is purchase_title limited to paid accounts? Is this a bug? Or is the purchase_title a field that is not officially supported and should be avoided?

Image 2023-02-03 at 8 50 48 AM Image 2023-02-03 at 8 49 14 AM

@rahul-sc

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the reported PUT and GET behavior for purchase_url and purchase_title across SoundCloud Next and Next Pro accounts. Review the public API behavior and the SoundCloud.com metadata editor evidence; done means establishing whether purchase_title is supported for all accounts, documenting the answer, or confirming a reproducible API defect.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.