Repost endpoint returning HTTP 429
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- api
Research direction
Start by comparing the reported /repost/tracks requests with the related issue 584 and reproduce the 429 response using the Swagger API explorer, multiple OAuth tokens, and separate IP addresses. Check whether the endpoint's rate-limit headers and behavior differ from other endpoints; done means identifying the cause and confirming the expected response or required API-side fix.
Written by the indexing model from the issue text.
Description
As mentioned in https://github.com/soundcloud/api/issues/584:
We seem to be getting nothing but HTTP 429 on the /repost/tracks endpoint, while other endpoints from the same machine(s) work perfectly fine. That endpoint also doesn't return any information about the rate limits in the response headers, while others return:
< x-ratelimit-limit: -1
< x-ratelimit-remaining: 0
< x-ratelimit-reset: 0
An example:
< HTTP/1.1 429 Too Many Requests
< Content-Type: application/json
< Content-Length: 38
< Connection: keep-alive
< Date: Sat, 26 Sep 2026 23:00:26 GMT
< server: istio-envoy
< vary: Origin
< x-generator: tyk.io
< x-tyk-trace-id: e6413ed89739db0e19ddd99ff0e55429
< x-envoy-upstream-service-time: 2
< X-Cache: Error from cloudfront
< Via: 1.1 08dc547306e2c7102196b53ce0859e80.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: FRA60-P11
< X-Amz-Cf-Id: PfWdzKD62C4OW1IeJJFLpzHI-6tJ1FPTbatn2vexuwe4VMtZa0u6aw==
Getting the same when sending from 2 separate IP addresses, with multiple different OAuth tokens (not sure which one rate limiting is tied to).
Also getting this when trying to send a request on the Swagger test page at: https://developers.soundcloud.com/docs/api/explorer/open-api#/reposts/post_reposts_tracks__track_urn_
Sent the application's Client ID to @SoundCloudDev on X.
- Dominant language
- JavaScript
- Stars
- 253
- Forks
- 53
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
soundcloud/api#591 ·
-
Terms question before registering an app: festival set library that links to artists' own uploadsOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
soundcloud/api#590 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
soundcloud/api#587 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
soundcloud/api#583 · 1 reaction ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#581 · 1 comment ·
Similar issues
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs:triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
mastra-ai/mastra#25508 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 72/100
githubnext/gh-aw-cao#15017 ·
Maintainers usually reply within 1 day