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.

We’ve added a new optional parameter openOnInsert to the configuration object in the manifest of Forge macros. This allows developers to control if the custom configuration modal is automatically opened when first inserted.

For more information, see Macro.

We have added support for the following request body fields for the Update custom content REST API V2 endpoint:

• spaceId

• pageId

• blogPostId

• customContentId

We have updated our UI Kit components, Text and Heading to make them more flexible:

Text

• Now supports align, as, color, maxLines, size and weight properties.

For more information, see Text component documentation.

Heading

• You can now control how the Heading component appears by setting a value for size, while the as prop controls the HTML element's rendering.

For more information, see Heading component documentation.

We are happy to announce we have added support for macro autoconvert to UI Kit. This allows your app to automatically insert a macro into the editor when a user pastes a recognized URL.

For more details, please see the Macro documentation.

Reminder: Starting Apr 30, 2025, a subset of Connect extension points will no longer be available on Confluence pages. For details, see the original deprecation notice linked below.

deprecation notice Deprecating a subset of Confluence page extension points

Action is required from developers using deprecated extension points.

The project addresses the integration of role-based access control (RBAC) in Confluence, focusing on its impact on apps and the ecosystem. The proposal suggests restricting apps from creating, updating, or deleting custom roles to prevent issues related to role limits per site. We are seeking feedback to determine if apps can continue updating user access using default roles and whether product admins should configure roles for apps to use.

https://community.developer.atlassian.com/t/rfc-91-role-based-access-control-in-confluence-roles-api-the-access-apps-can-set-with-it/90673

We’ve added V2 API endpoints to retrieve children and descendants for pages, databases, smart links, whiteboards and folders.

To enable these new V2 APIs, you’ll need to use the new Oauth 2.0 scope read:hierarchical-content:confluence.

These new APIs correspond to the following V1 APIs, which have been marked as deprecated (and will be retired on Apr 30, 2025):

• get content descendants

• get content descendants by type

We are extending the deprecation period for all endpoints noted in Deprecation of v1 Confluence Cloud API endpoints and Deprecation of v1 Confluence Cloud API Endpoints to April 30, 2025.

After the beta phase of Atlassian’s new navigation, we’re thrilled to announce its General Availability (GA) for Jira, Jira Service Management, Jira Product Discovery, Confluence, and Atlassian Home. In this article, you’ll find key details about what’s changing with the new navigation, Jira and Jira Service Management apps, as well as when those changes will go live.

Starting Sep 17, 2025, the ability to publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace will be deprecated. This change is part of our strategic shift to the Forge platform that enables developers to leverage enhanced capabilities such as Forge Storage.

Partners should plan to list any Connect apps currently under development on the Atlassian Marketplace by Sep 16, 2025, and should undertake all new app development on Forge.

Today we published Announcing Connect End of Support: Timeline and Next Steps, following up on our earlier blog post Taking the Ecosystem Forward: An Update on the Future of Connect.

This announcement is intended for developers of Connect apps, including partners and customers with custom apps. It provides a detailed view of the phases and timing for the end of support of Connect.