Newly getting 403ed

[k-andyman]

Hi Everyone,

I'm working on a research project for TU Berlin in the computational musicology team. I got an api access approved around half a year ago and am only retrieving publicly available data. My script that worked fine a few months ago started hitting 403s after just a few requests. It seems to be a CloudFront issue. (see debug answer below).

My SC username under which the APP is registered is andi-alphabet.
Any help would be much appreciated.

Thanks :)

--- STATUS ---------------------
[1] 403

--- HEADERS --------------------
$server
[1] "CloudFront"

$date
[1] "Mon, 24 Nov 2025 12:19:04 GMT"

$content-type
[1] "text/html"

$content-length
[1] "919"

$connection
[1] "keep-alive"

$x-cache
[1] "Error from cloudfront"

$via
[1] "1.1 634cb8ef257d85d9d03b5a4d492df944.cloudfront.net (CloudFront)"

$x-amz-cf-pop
[1] "TXL50-P1"

$x-amz-cf-id
[1] "YpjuXyboqPusntqyt-zT9bWPttAJ3CN3J0vG7QeoB9DJ8N7lWicCWg=="

attr(,"class")
[1] "insensitive" "list"

--- RAW BODY -------------------

<TITLE>ERROR: The request could not be satisfied</TITLE>

403 ERROR

The request could not be satisfied.

---

Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

---

Generated by cloudfront (CloudFront)
Request ID: YpjuXyboqPusntqyt-zT9bWPttAJ3CN3J0vG7QeoB9DJ8N7lWicCWg==

[dpreussler]

Hi there,
Your credentials look valid
What endpoint are you trying to call @k-andyman ?

[k-andyman]

@dpreussler

In my skript I use to call:

https://api.soundcloud.com/resolve?url=https://soundcloud.com//

Do you know if the /resolve endpoint has recently been restricted or anything alike?

Thx :-)

[dpreussler]

that i'm aware of, let me have a look

[dpreussler]

I see that your app created a lot of 401 (dont see the 403 from Cloudfront), like many thousands per day!
Are you refreshing your auth tokens properly?

[k-andyman]

Sounds like it might have been my mistake.
At the moment I can't obtain an auth token anymore (the token request returns 403), so I can't test anything further.
I'll try again tomorrow and see if that resolves it.
thx :-)

[youssefhassan]

Hey @k-andyman , are you still getting the 403s? Let us know

[jasongrishkoff]

Hi there, I'm getting 403s on all my token refreshes as well.

{
	"ok": false,
	"redirected": false,
	"data": null,
	"response": {
		"statusCode": 403,
		"headers": {
			"connection": "close",
			"content-length": "919",
			"content-type": "text/html",
			"date": "Fri, 12 Dec 2025 21:34:13 GMT",
			"server": "CloudFront",
			"via": "1.1 153c5cd2b3e635613d0a2fa0f107993a.cloudfront.net (CloudFront)",
			"x-amz-cf-id": "TZrhrFSPhMfcdj5jllwUTJgio4wzt5B3WcOYDDXkD2ybSRbCQLcyKQ==",
			"x-amz-cf-pop": "JFK50-P3",
			"x-cache": "Error from cloudfront"
		},
		"content": "403 ERROR\n\nThe request could not be satisfied.\n\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n\nIf you provide content to customers through CloudFront, review the CloudFront documentation for troubleshooting steps.\n\nGenerated by CloudFront\nRequest ID: TZrhrFSPhMfcdj5jllwUTJgio4wzt5B3WcOYDDXkD2ybSRbCQLcyKQ=="
	}
}

[ymeskini]

Yeah, same here cc @youssefhassan @dpreussler, though it seems to be fixed

Edit: it's still happening again

[sabato-galasso]

Yes, here too cc@youssefhassan @dpreussler, even though it seems to be fixed.

Edit: It's still happening again.

I confirm, it seemed fixed, but then it came back.

[julienbornstein]

Same issue here.

When calling endpoints from our production servers the API return a 403.
When i'm running the same curl request (same token, same headers ...) from an other machine (local computer) I get a valid (expected) HTTP response

Request :
https://api.soundcloud.com/resolve?url=https%3A%2F%2Fsoundcloud.com%2Fofficialmetallica

Response :

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: 48rjCMBomzOc4mRCC9IVGESr_GifQ5K1HTzQ7lbYynQNXv0kQdhyAw==
</PRE>
<ADDRESS>
</ADDRESS>`

[ductridev]

It happens with me even on the website, not sure my IP got blocked or sth. Request id s2oe1YJVfkgtm2jHVTbtLD_EzQM4VQ6vrO9mgGqfgzt39b71vSxsNQ==

[ymeskini]

@dpreussler could you please communicate about what is happening? The API has not working since Friday....