Is purchase_title officially supported?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api
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.
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_urldoes not cause an error - PUT
purchase_titledoes not cause an error - GET
users/{id}/tracks/{track_id}return contains updatedpurchase_url, but nullpurchase_title
SoundCloud Next Pro User - Updating works for this users
- PUT
purchase_urldoes not cause an error - PUT
purchase_titledoes not cause an error - GET
users{id}tracks/{track_id}return contains updatedpurchase_titleandpurchase_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?
@rahul-sc
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from soundcloud/api
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#581 · 1 comment ·
-
widget
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#557 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
soundcloud/api#548 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#547 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#545 · 2 comments · 1 reaction ·
Similar issues
-
status: waiting triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
freeCodeCamp/freeCodeCamp#70412 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Jason-Vaughan/TangleClaw#1884 ·
Maintainers usually reply within 1 day
-
bug good first issue web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/TypeScript#64453 ·
Maintainers usually reply within 1 day
-
self-driving
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day