API returning HTTP 403 CloudFront errors

Trying to access https://api.trello.com/1/members/me/boardStars

<!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>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Bad request.
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">
Generated by cloudfront (CloudFront)
Request ID: sb4hE3E_eC-tX-b_7bwFw9XR2y5ZR6oG5AiMkJCyNQoIelvGHdWKCg==
</BODY></HTML> at https://api.trello.com/1/members/me/boardStars (HTTP status: 403)

Hello @Mattlassian

I can currently access that Trello REST API endpoint with no issues or errors/

Still seeing this (for the last 7 hours) when accessing the API via OAuth tokens. API tokens in the URL don’t seem to be an issue.

Same here. The API occasionally returns 403 CloudFront errors since yesterday.

Same here…

Atlassian support let me know it should be fixed now

It must have been an intermittent or regional / time zone issue, as I didn’t get that problem where I am.

This is happening again since 12:31pm ET

Just started getting this error as well today. Tried looking it up and it seems to be something relatively recent. Is it safe to assume this isn’t a client error but a server error?

Also experiencing API returning HTTP 403 CloudFront errors

Atlassian developer changelog - Trello’s API will no longer permit supplying a body with a GET request. Previous behavior in our API ignored the payloads provided with GET requests but these requests will now be blocked with a 403 response from our content delivery network.

To resolve issues resulting from this change ensure all GET requests to Trello’s API are sent without a payload. - if using an open source library like py-trello you will need to refactor your code.

This issue is still happening to me