Changelog

Atlassian Marketplace is transitioning to a scalable architecture by reengineering our monolithic data model and adopting a microservices-based approach to enhance reliability and scalability. With this, Marketplace partners will see some changes which will require adoption.

Key changes for Marketplace partners:

• Transition from V2 APIs:

  • Marketplace v3 REST APIs: We are making changes to the Marketplace APIs(https://developer.atlassian.com/platform/marketplace/rest/v2/intro/#), which will include deprecations—some with replacements (v3 APIs) and others without. The new v3 APIs will be available from Jun 30, 2025.

  • Deprecation of REST V1 APIs: All v1 APIs are deprecated and removed. To avoid disruptions, transition to v3 APIs.

• User experience enhancements: We are improving visual design of some of our experiences. These updates primarily focus on modernizing the tech stack and aligning with Atlassian Design Systems, replacing older designs.

For more information on implementation details and release dates, have a look at the Quick Reference Guide. Let us know your feedback as comments on the QRG.

Multi-instance licensing is now live!The Atlassian Marketplace has introduced a new level of flexibility in app billing and licensing. This enhancement allows Cloud Enterprise customers to be charged based on the number of unique users of the app across multiple instances, irrespective of the number of product instances.

Customer GA is targeted for May 2025. The capability to set multi-instance pricing for apps is available from today, Feb 20, 2025. We recommend planning and setting your new pricing by May 15, 2025.

• Multi-Instance Pricing: Partners must offer multi-instance pricing for paid cloud apps alongside single-instance pricing, with flexibility to set different prices.

• Existing Apps: Multi-instance pricing will be enabled by default, initially matching single-instance pricing.

• Default Pricing: The pricing console will default multi-instance pricing to 1x of single-instance pricing, but partners can adjust this multiplier or edit fields as needed.

• Customization: Partners can set multi-instance pricing as a price multiplier (≥1x of single-instance pricing) and edit pricing across different user tiers.

We have identified an issue within our system that resulted in the absence of customer feedback on churn events via the Feedback APIs between January to February 2025.

This issue has now been resolved, and consequently, 167,332 customer feedback records will be made available across all partners. These customer feedbacks were generated during the period from August 2020 to the present date. Effective Feb 20, 2025, partners will gain access to customer feedback regarding churn events from both historical and current feedback through reporting, as well as via the following APIs:

• Get feedback

• Export feedback

• Get aggregated feedback

We have recently noticed an unusual increase in API usage. In order to maintain reliable services for both Atlassian customers and partners, we will begin enforcing more granular rate limits for Confluence and Jira APIs.

We will begin enforcing REST API (Quota and Burst based) rate limits for all free apps on or after August 18, 2025. We have added additional headers to provide further transparency. Please monitor header responses to see where you are at with regard to limits.

In some circumstances where apps are highly impacting the stability of our platform, we reserve the right to enforce the limits at an earlier date. We will notify your listed contact via email if you are impacted. Additionally, we are planning to bring clarity to rate limits across our platform infrastructure over the next year, including paid apps.

We recommend all customers and partners ensure they're not exceeding the rate limits so that they do not get impacted at a later date.

Learn more about the header responses and read relevant FAQs about rate limiting adjustments for Jira here and Confluence here.

We're excited to announce that we’re expanding the early access program (EAP) for App Editions to more partners. Our goal this time is to engage additional partners who have previously expressed interest and those who have recently shown enthusiasm for developing editions.

This approach will ensure readiness when we activate the customer General Availability (GA) switch, also known as Milestone 3, in Q2 of calendar year 2025. We have a quick but involved path from EAP to General Availability and are looking for our early adopters to work with us along the way.

Learn more about the EAP participation criteria and requirements here. If you’re interested in participating in the early access program Round 2, please complete the attached form by Mar 3, 2025.

Starting Feb 18, 2025 , we are introducing two updates:

1. New Billing System Field (newBillingSystem) in Marketplace reporting Licensing API

   • This field indicates whether a customer entitlement is on the new or old billing system.

   • Yes = Entitlement is on the new billing system

   • No = Entitlement is still on the old billing system

   • If case of free apps data this fields  is not available

   • This is particularly important for Marketplace partners participating in App Editions, as it helps identify which cloud customers are on the new vs. old billing system.

   • The field will be maintained when a customer transitions between billing systems.

2. Dual Licensing Discount Reason Code in Marketplace reporting Transactions API
   We have backfilled data for 62,000 transactions across various partner accounts to correctly display dual licensing discounts for records that were not displaying it earlier. These records were originally not displayed as DUAL_LICENSING but are now correctly labeled. To improve accuracy, we have enhanced our pipeline to map a specific internal reason code(which previously was a free text field) to dual licensing.

   Partners can access these discounts via the Transactions API and read the following fields:

   • Discount Type: Manual

   • Reason Code: DUAL_LICENSING

Multi-instance licensing will soon be available. This licensing model will enable Cloud Enterprise customers to be charged based on the number of unique users of the app across multiple instances, regardless of the number of product instances. We are aiming for Customer GA in May 2025. However, the capability to set multi-instance pricing for apps will be available on Feb 20, 2025.

To facilitate a seamless rollout of multi-instance licensing (MIL), we will block set pricing updates for three days (February 17th to 19th, 2025) prior to the multi-instance partner release on Feb 20, 2025. This pause will allow us to run migration and validate APIs effectively.

We have resolved several data inconsistencies in the Marketplace Reporting Licenses API caused by edge cases/scenarios supported on our new billing system.

As part of these corrections, we have updated key fields like maintenanceEndDate, licenseType, and status for approximately 10,000 active license records created or migrated to the new billing system across all Marketplace partners' data. Additionally, about 500 licenses have been corrected for fields such as hostEntitlementNumber, hostEntitlementId, parentProductBillingCycle, parentProductEdition, partnerDetails, unit_count, and tier

These changes will be deployed to production on Wednesday, February 12, 2025. You can retrieve updated records based on timestamp changes.

• When a customer moved from annual to monthly billing, the maintenanceEndDate previously retained the annual end date. This has now been corrected to reflect the current billing period's end date.

• In cases where customers canceled a paid period and created a new one, license records were not correctly updated.

Some inactive licenses were impacted, for which the data is also fixed. If needed, you can pull inactive license data to refresh your pipelines and ensure your records reflect these corrections.

We are updating the look and feel of the "App details" flows in the partner portal. The functionality of the different components will remain the same and the updates are limited to visual changes only.

Initially, a small percentage of partners will gain access to these updates, with a phased rollout planned for all partners to complete by Feb 14, 2025. For more information, please refer to the Quick Reference Guide(QRG) here.

Permission changes towards the reduction of domain egress of your app are now treated as a a minor update.

For example, while previously triggering major updates, the following external egress permission changes now trigger a minor update:

• Updating {"IMAGES":["*"]} to {"IMAGES":["any list of domains"]}

• Updating *.media.atlassian.com to https://api.media.atlassian.com

As such, we encourage partners to improve the trust posture of their apps by reducing the egress or improving the transparency of the app egress.

As announced early Sep https://community.developer.atlassian.com/t/we-are-making-app-management-easier-for-our-cloud-admins/83303 we are now in the final phase of moving the in-product app management experience (UPM) across to Connected Apps which can be accessed from admin.atlassin.com.

The app management entry point in products will remain and we will start to progressively direct admins to Connected Apps

Roll out start: 10th Feb 2025

Roll out end: 19th Feb 2025

We understand many of you are just getting back from the holidays and are also gearing up for Atlas Camp next week. Due to this, we will be pushing the hard block from Jan 31, 2025 to Feb 14, 2025 to provide you with some additional time, learn more here

For apps still in violation, we will work in close collaboration with you, and you will receive further communication outlining the subsequent steps to resolve the violation.

On Feb 15, 2024, we officially ended support for our server products. Customers were no longer able to purchase, renew, upgrade, or receive any further support for all Jira, Confluence, Bitbucket, Bamboo, and Crowd server apps.
In June 2025, we will be removing the Server listings from the Atlassian Marketplace. Post these changes for all apps (besides Fisheye and Crucible) -

1. Server-only app listings will be removed from the Marketplace.

2. Server pages for apps with server hosting type will be removed.

For more information and nuances, please check this QRG.

Following the deprecation announcements on October 24, 2024, and November 14, 2024, we have now removed the V1 Marketplace APIs.

Please switch to the applicable V2 alternatives listed in the More Details section.

We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com