Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Is the /rest/api/3/myself API working for anyone? I am now getting a 403 response from Cloud Front

Is the /rest/api/3/myself API working for anyone? I am now getting a 403 response from Cloud Front

Chris Dunn
September 3, 2026

I am suddenly receiving an unsuccessful status code (403) from the `/rest/api/3/myself` API endpoint (see the api doc here).   I am sending the request to `https://{my-account}.atlassian.net/rest/api/3/myself`.

Is this API working for anyone else? my personal access token is still valid and hasn't expired, and I've checked I'm sending the token using Basic Authentication.  I've also tried accessing the API via `https://api.atlassian.com/ex/jira/{my-cloud-id}` using both a granular and classic scoped token for an Atlassian service account (using Bearer Authentication) and I still get the same error.

This used to work fine and then a day or so ago it stopped working and I started receiving a 403 response. 

Is there a problem? the Atlassian service status pages are reporting no error.  

Here is the actual response I get: 

<!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">
    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">
    <PRE>
Generated by cloudfront (CloudFront)
Request ID: ....
</PRE>
    <ADDRESS>
    </ADDRESS>
</BODY>

</HTML>

1 answer

1 accepted

0 votes
Answer accepted
Chris Dunn
September 3, 2026

Problem fixed.  Turns out myself contained a body, which I hadn't noticed.  Removed the body and the request started working again.  Doh, thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events