I need to contact a Confluence admin

[Daniel A Palomar1]

Hi Team,

I need help with Confluence API access for automation on tenant aexp.atlassian.net.

When running our Confluence automation scripts, all Confluence REST calls return:

• HTTP 403 Forbidden
• {"message":"Current user not permitted to use Confluence","statusCode":403}
• Local setup is complete (.venv, dependencies, env config, proxy path).
• API token is stored and retrievable from secure keyring.
• Proxy connectivity is working (requests reach Confluence endpoint).
• Multiple page IDs were tested and all fail with the same 403
• Authenticated user should be able to read Confluence pages via REST API.

[Aaron Pavez _ServiceRocket_ · Accepted solution]

Hi @Daniel A Palomar1 

> I need help with Confluence API access for automation on tenant aexp.atlassian.net.

Whats the API you are running? have you tried using your own API token and email to make the call?

Test the API in post man first, then move it to the automation.

Maybe you are missing the encode base64?

Send us a couple of screenshots of the automation to understand how are you calling the API. any other details are welcome.

Regards

[Daniel A Palomar1]

Hi Aaron,

Thanks for the quick response.

I’m calling this API:

GET https://aexp.atlassian.net/wiki/rest/api/content/2091981194?expand=body.storage,version,space

I tested with my own Confluence email and API token (Basic auth with Base64 email:token), both in script and direct PowerShell/API call.

Current behavior from my environment:

• Direct reachability test to Confluence endpoint returns:
  • STATUS=407
  • STATUS_DESC=AuthorizedOnly
• This indicates corporate proxy/ADS authentication is failing before Confluence can process the request.

• Command used for reachability test:
• Invoke-WebRequest "https://aexp.atlassian.net/wiki/rest/api/space" -UseBasicParsing -TimeoutSec 30
• So at this point the blocker appears to be proxy authentication (ADS/proxy credentials), not Base64 encoding logic in the automation.
• Could you please help verify/reset my ADS proxy access and allow outbound proxy authorization for aexp.atlassian.net

Thanks

Daniel

[Daniel A Palomar1]

Hi Team, 

Please find additional evidence from the automation call.

I ran:

.\.venv\Scripts\python [update_action_tracker.py](http://_vscodecontentref_/2) list

Result:

urllib.error.URLError: <urlopen error Tunnel connection failed: 407 AuthorizedOnly>

This indicates the request is blocked at the corporate proxy tunnel (HTTP 407) before the Confluence API can be reached.
Could you please verify/reset my ADS/proxy authorization and allow outbound proxy access for:

• https://aexp.atlassian.net
• https://aexp.atlassian.net/wiki/rest/api/*

I’ve attached screenshots of:

1. direct Invoke-WebRequest test
2. automation traceback showing 407 AuthorizedOnly.

Thanks

[Aaron Pavez _ServiceRocket_]

Hi again @Daniel A Palomar1 

As mentioned by @Marc -Devoteam- , this is something on your side.

You need to contact your Jira admin and IT admin to help you check any proxies or anything hindering the communication to your confluence. 

Regards

[Marc -Devoteam-]

Hi @Daniel A Palomar1 

Welcome to the community.

Here on the portal we can't grant access to instances. This is a public community forum for users of Atlassian product to help each other, but we can't access instances or grant access to instances.

Not even official Atlassian Support will honour such a request.

You will need to contact an admin of the instance or the IT department of the company the instance belongs to.