Send web Request - 403 error

[Tomasz Osik]

Hi, 

I am trying to schedule a call from Jira to confluence, at certail time to:

- Get Page (content)

- Generate email with content (html) and send it over

I have:

- Generated API Token

- Make sure that actor have access to confluence and jira. 

I have config:
Web Request URL -->https://XXXXX.atlassian.net/wiki/rest/api/content/762970113?expand=body.view

HTTP Method: GET

Web request body -->Empty

Authorisation: Basic [encoded email:apitoken]
content type - App/Json

I am keep getting back:

{

    "message": "Current user not permitted to use Confluence",

    "statusCode": 403

}

from both, Jira automation and postman

Can someone advise me where i am making mistake?

[Bill Sheboy]

Hi @Tomasz Osik 

Which endpoint are you trying to use?

To get a specific page's content, please try this one: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-id-get

Kind regards,
Bill

[Tomasz Osik]

Hi Bill,

I have checked if my Confluence Token scope is correct:

I am using Confluence API as Jira does not allow to call it. Yet I am having 403 on each occasion. I am loosing my mind here as i have spend 2 days already on something simple :) i would appreciate your help. 

[Bill Sheboy]

Again, which endpoint are you trying to use?  Please provide the doc reference to confirm we are seeing the same thing.

In the meantime, have you tried using the endpoint URL directly in a browser tab?  I believe the page content one will work when you have it correctly specified.

[Tomasz Osik]

Hi Bill,

https://xxxxxxx.atlassian.net/wiki/api/v2/pages/762970113?expand=body.view

Using GET Page by ID

https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-id-get

and i have tried to use it directly in browser. Returns:

      

So looks like it is returning values. 

[Tomasz Osik]

Hi, 

I keep receiving 404 error. So there must be something with my token and/or actor. Even though i am an admin on confluence, cannot access it? seems odd. Token looks ok, i know that APIs must be scoped, which is good. I have tried user ID and not email as a bearer, basic with email, user id and token. 

Nothing works.

[Bill Sheboy]

Was your API token created with the same user with which you are logged in when trying from the browser tab?