You can now specify what actions an API token has permission to perform. When you create an API token from your Atlassian account, you can select the scopes for the API token. This change enhances security by allowing you to define specific permissions for API tokens.

We’ve added 3 new Confluence bridge APIs to improve how Forge apps can interact with Live Docs. When editing a Live Doc or Page, the content within the editor can be ‘ahead’ of its latest snapshotted or published version. These new Confluence bridge APIs allow Forge apps to interact with that latest content in the editor, even if it hasn’t been snapshotted or versioned yet.

1. getEditorContent - Return an ADF object representing the latest editor content of an entire document.

2. getMacroContent - Return an ADF object of the current Forge extension macro.

3. updateMacroContent - Update the content of the current Forge macro.

Read more detailed documentation about these new Confluence bridge APIs here.

As of today May 1, 2025, the following deprecated Confluence REST API V1 endpoints have been removed from service. This means requests to these endpoints will result in a 410 error response. These endpoints have also been removed from REST API V1 documentation.

• Get Content: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content/#api-wiki-rest-api-content-get

• Create Content: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content/#api-wiki-rest-api-content-post

• Get Content By ID: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content/#api-wiki-rest-api-content-id-get

• Update Content: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content/#api-wiki-rest-api-content-id-put

• Delete Content: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content/#api-wiki-rest-api-content-id-delete

• Get Content History: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content/#api-wiki-rest-api-content-id-history-get

• Get Attachments: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content---attachments/#api-wiki-rest-api-content-id-child-attachment-get

• Get Content Children: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content---children-and-descendants/#api-wiki-rest-api-content-id-child-get

• Get Content Children by Type: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content---children-and-descendants/#api-wiki-rest-api-content-id-child-type-get

• Get Content Comments: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-comments/#api-wiki-rest-api-content-id-child-comment-get

• Get Label for Content: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-labels/#api-wiki-rest-api-content-id-label-get

• Get Content Versions: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-versions/#api-wiki-rest-api-content-id-version-get

• Get Content Version: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-versions/#api-wiki-rest-api-content-id-version-versionnumber-get

• Get Inline Task based on Search Parameters: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-inline-tasks/#api-wiki-rest-api-inlinetasks-search-get

• Get Inline Task based on Global ID: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-inline-tasks/#api-wiki-rest-api-inlinetasks-inlinetaskid-get

• Get Spaces: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-space/#api-wiki-rest-api-space-get

• Get Space: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-space/#api-wiki-rest-api-space-spacekey-get

• Get Content for Space: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-space/#api-wiki-rest-api-space-spacekey-content-get

• Get Content for Space by Type: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-space/#api-wiki-rest-api-space-spacekey-content-type-get

• All Space Properties endpoints: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-space-properties/#api-wiki-rest-api-space-spacekey-property-get

• All Content Property endpoints: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-properties/

• Update inline task given global ID: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-inline-tasks/#api-wiki-rest-api-inlinetasks-inlinetaskid-put

As of today Apr 30, 2025, the following Connect extension points will be removed from Confluence Cloud (see our deprecation notice from six months ago here):

• page.metadata.banner

• atl.page.metadata.banner

• system.content.button

• atl.editor.savebar

• system.editor.precursor.buttons

• system.content.metadata

Also, the following Connect extension point will no longer render a UI component on Confluence pages, but can still be used for running background scripts only.

• atl.footer

Note that we are gradually rolling out this removal to customers. That means, in some instances you may still see the above extension points in Confluence Cloud. Understand that they may be removed at any point.

Developers using any of the removed Connect extension points should actively consider (if not already) transitioning to the following available extension points. This move is crucial to ensure app and experience continuity for end-users.

• Forge

  • confluence:contentBylineItem

  • confluence:contentAction

  • confluence:contextMenu

• Connect

  • system.content.action/secondary

  • contentBylineItem

  • system.content.action

  • system.content.action/primary

  • atl.general

  • system.content.action/modify

  • page.view.selection/action-panel

  • system.content.action/marker

Note that these changes only apply to extension points available when interacting with Confluence pages and live docs. Any extension points beyond the context of a Confluence page or live doc are not impacted.

We’ve released a new Background Scripts module, which enables apps to run in the background of a Confluence page. See Confluence Background script for more information.

You can use background scripts to replace the atl.footer extension point in Connect.

Internationalization (i18n) for Forge apps is now generally available. This allows you to add translation support to your app so that it can adapt based on a user’s language and locale.

In addition to the Confluence and Jira modules that were supported during the EAP, internationalization support can now also be added to Bitbucket, Compass, and Jira Service Management modules, as well as Forge resolvers.

For more information, see Internationalization.

Live docs are coming to Confluence Cloud as new content type alongside existing Pages. Live docs can be updated instantly without having to publish, allowing teams to quickly collaborate on content. All sites in the Developer Canary Program have access to Live docs (as of November 2024).

We are asking developers to test their apps in Live docs and make sure that they are functioning as expected by May 30, 2025.

See more technical guidance on Live Docs in our developer community post here. We are also working on including all details in official documentation on developer.atlassian.com where relevant, but wanted to share with developers ahead of time.

Forge Remote Data Residency realm migrations is now available in GA. This release provides apps with the ability to support customer-initiated migrations between data residency regions.

Please review the documentation to learn more about how to support realm migrations in your app.

We’ve added a new V2 REST API for the admin key feature for Confluence Cloud Premium and Enterprise customers.

This API can be used by organization or site admins to retrieve, enable, and disable admin keys for their users.

Go to the documentation to read more about this API.

Organization or site admin users in Confluence Cloud Premium and Enterprise instances can make calls to any of our public REST APIs using an Admin Key by adding the following HTTP header to their requests:

HTTP Header Name: Atl-Confluence-With-Admin-Key

HTTP Header Value: true

If the calling user doesn’t have an active admin key granted to them at the time of the request, this HTTP header will simply be ignored.

We’re happy to announce that subtype is now available via Forge’s useProductContext hook, to help Forge apps determine if a page object is a Live Doc or a Page.

Now, the extension object returned from the useProductContext hook will return subtype: 'live' if a given page object is a Live Doc. Otherwise, it will return subtype: null

This change should be immediately available on sites in the Developer Canary Program for your testing purposes.

We’re happy to announce that subtype is now available via AP.context.getContext() for Connect apps, to help them determine if a page object is a Live Doc or a Page.

When a content object of type: ‘page' is returned, it will return subtype: 'live' if it is a Live Doc, or subtype: '' if it is a Page.

This change should be immediately available on sites in the Developer Canary Program for your testing purposes.

We are extending the deprecation period for the following V1 REST APIs:

• get content descendants

• get content descendants by type

These APIs will be retired on Sep 30, 2025 (the date for retiring these was previously announced as Apr 30, 2025):

Additionally, the V2 API endpoint to get child pages will be retired on Sep 30, 2025.

Please use the new V2 APIs announced in changelog entry instead.

We are extending the deprecation period of the Convert content body v1 REST API in Confluence Cloud to Aug 1, 2025.

The Confluence team is utlizing the additional time to address and fix bugs in the alternative Asynchronously convert content body endpoint, such as the issue tracked under CONFCLOUD-81273.

We will not be issuing any new waivers for apps that need to request or store Atlassian user API tokens. This decision is part of our ongoing commitment to enhancing security and protecting customer trust.

Forge Apps that have already been granted waivers must ensure a lack of alternative solutions within Forge. They can continue to operate, but no additional waivers will be granted for new modules or new functionality within the same app.

Connect apps that have been granted waivers and any existing Connect app requesting or storing Atlassian user API tokens are required to migrate to Forge, with tokens stored in Forge encrypted storage.