Confluence page creation through API will be deprecated soon, and there is no replacement

[Daniel de Cordoba Gil]

In my Jira Service Project, I have an automation rule to create a Confluence page on issue creation. I use this endpoint to do this:

• https://{your-domain}.atlassian.net/wiki/rest/api/content

But when doing this I am getting the following warning.

• Deprecated API, will be removed on Mon, 2 Dec 2024

According to what I have found, my new endpoint should be:

• https://{your-domain}/wiki/api/v2/pages

But when calling it, and changing the request structure to the new one, I get a 404 saying the endpoint does not exist.

How to fix it? I don't want my automation to stop working in 2 months, and all tutorials on these kinds of automation refer only to the old API, not the new one.

Thanks!

PS: In case you need to know, the reason why I don't use the Creat Page in Confluence action in automation is because it does not allow to specify smart values in the body of the page.  

[Daniel de Cordoba Gil · Accepted solution]

Turns out, my authorization was incorrectly configured.
The 404 was still responding NOT FOUND only, but I guess that is for safety.

Same as before, headers need to contains an Authorization field, with value "Basic <base_64_api_token>"

[Lukas Nicolai_Seibert]

Hey @Daniel de Cordoba Gil , if Atlassian is deprecating an API, I would suggest our app, AutoPage. You can easily create Confluence pages from Jira issues and add smart values to the body of the page. Hope that helps! :)

[marc -Collabello--Phase Locked-]

Can you post a screenshot of the details of your automation?  A 404 response could also mean that permissions are not ok.