On February 10th 2025, we announced the Deprecation of automation.atlassian.com incoming webhooks for Automation rules https://developer.atlassian.com/changelog/#CHANGE-2299. As of 30 May 2025, the legacy incoming webhook has now been deprecated.

Atlassian font assets are now being preloaded by the Connect JS library (ACJS) to support consistent typography across Atlassian and Connect apps. These assets are served from dedicated design system CDN https://ds-cdn.prod-east.frontend.public.atl-paas.net.

Connect apps using the standard all.js ACJS bundle will now automatically pre-load:

• atlassian-fonts.css

• Atlassian Sans font files (e.g., AtlassianSans-latin.woff2)

These files are delivered from the new ds-cdn host. The change was previously gated and is now enabled for all Connect apps.

Apps with a strict Content Security Policy (CSP) must update their style-src and font-src directives to allow the new CDN host. Without this, CSP violations may block font and styles loading.

Update your CSP to include:

We’ve added new Confluence product events for labels:

• avi:confluence:created:label

• avi:confluence:added:label

• avi:confluence:removed:label

• avi:confluence:deleted:label

You can use these events to invoke your Forge app function when label is created, added to an entity, removed from an entity, or deleted. For more details see https://developer.atlassian.com/platform/forge/events-reference/confluence/#labels.

With the Forge CLI 11.5.0 release, we've enhanced the Forge platform to let you specify the memory available to functions at runtime by setting the memoryMB property in the Manifest (https://developer.atlassian.com/platform/forge/manifest-reference/#runtimev2) . Increasing the function memory also increases its CPU allocation. The memory value can now be set between 128 MB and 1,024 MB, doubling the previous limit of 512 MB. If you do not configure the function memory, the default memory allocation of 512MB applies to your function. This change helps address out-of-memory (OOM) issues by allowing higher memory allocation.

We’ve released a new module, Confluence page banner, which enables apps to add a banner to Confluence pages. This module is generally available.

We are deprecating the following Atlassian Connect-related unscoped npm packages in favor of their @atlassian scoped equivalents.

Starting 23rd of June 2025, these packages will no longer be supported, and we recommend transitioning to the corresponding scoped packages instead.

The affected packages are:

The scoped packages maintain 100% API compatibility with their unscoped versions, ensuring a seamless migration experience. We recommend updating to the scoped versions as soon as possible before the deprecation date.

All of these packages are part of the Atlassian Connect ecosystem and are used for developing Connect apps. The scoped packages provide identical functionality but align with our standardized package naming conventions. This change helps ensure consistency across our npm ecosystem and improves package security.

To update your dependencies, replace the unscoped package names with their scoped equivalents in your package.json files.

If you encounter any issues during migration, please reach out through the Developer Community forums.

• We’re notifying you regarding the use of API tokens. Starting November 22, 2025, Atlassian will implement rate limits for API tokens to ensure a consistent, reliable, and secure experience for all users.

• If you are using API tokens, please review this documentation to learn more about the limits

  • Jira documentation

  • Confluence documentation

• In some circumstances, where integrations using API tokens heavily impact the stability of our platform, we reserve the right to enforce the limits at an earlier date. If you will be rate-limited before November 22, 2025, Atlassian will contact you directly.

• The introduction of rate limits is a proactive measure to safeguard our platform's stability and security. Rate limits help ensure platform stability and reliability by preventing integrations from overloading Atlassian’s systems.

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.