Changelog

We're excited to announce a new, live feature that allows Marketplace Partners to display verified third-party trust center links on their app listings and partner profiles. This initiative aims to enhance transparency and build trust by giving customers easy access to verified compliance and security information.

Adding this link is optional but as part of the recent updates to the Marketplace Partner Program, it will become mandatory for Platinum partners to include links to a third-party verified trust center starting in July 2025.

Marketplace is updating the logic for calculating the saleType provided via the transactions report.

To determine the sale type within transactions, we currently rely solely on the difference in user count from previous transactions.

With the upcoming improvements to the sale type:

• The type of sale will be defined by the interplay between the gross list price and the editions offered. The gross list price represents the total amount a customer must pay based on the listed price, without accounting for any deductions or adjustments. This approach shifts our focus away from fluctuations in user count to a more inclusive logic. Changes in either of these factors will influence the sale type, with greater emphasis placed on the gross list price. For instance, the gross list price goes up while the customer downgrades their edition. The sale type will consider both these factors and with a higher emphasis on change in gross list price, the sale type will be UPGRADE.

• We are introducing a new sale type referred to as DOWNGRADE. If there is a reduction in the gross list price compared to previous transactions, or if the edition is downgraded while the gross list price remains unchanged, the transaction will be classified as a downgrade.

• The same will be reflected in the user experience for partner reporting

We encourage our partners to gain a comprehensive understanding of the new logic. For more details, refer to the quick reference guide.

From Apr 30, 2025, uploading visual marketing assets through app artifacts (.jar, .obr, or .jwb) will no longer be supported. Instead, partners now have the option to use either the UI or the APIs to upload their branding assets, both of which are already available.

You can continue to upload your software using the existing option or the API. However, to upload marketing assets, you must use the publish experience or the API and upload the assets during that process, rather than using the app artifact upload option.

This change is part of the broader Marketplace Technical Foundations initiative.

For any comments or questions, please submit a support request.

We have identified an issue with the display of Solution partner type & solution partner billing contact emails in our reports.

Previously, partner type field, partnerDetails.partnerType displayed ‘Unknown’ for 26,000 transactions in transactions API across Marketplace partners.

Additionally, in partner detail, the billing contact email and name field -partnerDetails.billingContact for solution partners incorrectly displayed Atlassian email addresses for some licenses in licenses API across Marketplace partners.

These issues have now been corrected as of Mar 21, 2025 . Marketplace partners can access accurate Partner types and billing contact emails using the lastUpdated field in the in the Get licenses and Get transactions API respectively.

We have identified an issue with the display of license status and licenseType for Sandbox licenses migrated to the new billing system. Post-migration, these licenses incorrectly displayed status as Cancelled and licenseType as Commercial on the licenses API and Marketplace reporting user interface.

This issue is now fixed and the migrated sandbox licenses correctly display active status and FREE licenseType for ~ 10k license lines across all Marketplace partners. The updated records for Sandbox licenses can be identified using the following fields and values in the Get licenses API:

• installedOnSandbox - Is Sandbox

• status - Active

• licenseType - FREE

Marketplace Partners can access updated license records using the lastUpdated field.

We're introducing new app pricing tiers for up to 150,000 users for Confluence and Jira Data Center apps to better support our enterprise customers. You can update the pricing for the new tiers of your paid apps to ensure a seamless buying experience for customers. This change will take effect from March 17, 2025.

On February 18th, we announced that we will begin enforcing REST API (Quota and Burst based) rate limits for all free Jira and Confluence apps on or after August 18, 2025 and that we have added additional headers to provide further transparency.

To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:

• Beta-Retry-After

• X-Beta-RateLimit-NearLimit

• X-Beta-RateLimit-Reason

• X-Beta-RateLimit-Reset

However, if you do receive headers without beta-, be advised that you are facing rate limits.

We have identified an issue in the cloud churn, conversion and renewal charts computation for paid apps with cloud and Data Center/Server hosting type. Specifically, Cloud churn, conversion and renewal was computed at the app level,

Meaning, if the Data Center/Server version of an app transitioned from paid plan to free plan for a certain time period, while the cloud version continued to be on paid plan, the cloud churn was not computed during that time. Consequently, this led to inaccuracies in the calculations for cloud churn, as well as renewal and conversion counts within the specified timeframe.

This issue has now been resolved, and effective Mar 12, 2025, Marketplace Partners can check accurate cloud churn, renewal and conversions computation in reporting section of Partner accounts as well as the following APIs

• GET Cloud Churn

• GET Cloud Renewal

• GET Cloud Conversion

Starting March 10th, 2025, we will create new annual review tickets for the Cloud Fortified Apps Program and Data Center apps. You now have up to 60 days to complete your annual reviews and you will receive ample reminders to ensure smooth renewal for your apps. You will also have access to the initial review and the previous years' annual reviews for as long as you are mentioned in the Request Participants field. Any changes to request participants will be replicated across all linked tickets to ensure access to your apps' historical annual reviews.

We have identified an issue with the display of discount information for refund transactions. Up until today, refund transactions with discount amount for the following discount types:

• EXPERT

• MANUAL

• MARKETPLACE_PROMOTION

were displayed inaccurately, failing to incorporate the summation of both Atlassian and Partner discounts.

• This issue has been rectified, and the discount amount for each type is calculated as the sum of Atlassian and Partner discounts. We have backfilled the correct discount amounts for 11,000 records across Marketplace Partners. Partners can now access total discount value for the above discount types in the following APIs:

  • Get transactions

  • Export transactions

  • Initiate Async Export transactions

• Implementation Date: The updated discount information will be accessible to partners commencing March 7, 2025. Partners can fetch updated records by the checking the lastUpdated field for the above mentioned APIs.

We're excited to announce the launch of a pilot program for App Bundles on Marketplace!

We are looking for early adopters to work with us along the way.

What are bundles?

App Bundles represent a curated collection of multiple apps, offered to Marketplace customers as a cohesive package for purchase. Bundles enable partners to sell a collection of apps that work better together while simplifying decision-making and streamlining customer purchasing.

How will the pilot work?

The pilot will include the creation of a unified discovery experience of apps in the form of a single bundle listing. We will be using discount codes to provide a lower price point for apps in a bundle as compared to set pricing for individual apps

For the pilot, a select group of partners will be able to participate and create bundles on Marketplace. Interested in being a part of it? Please take a look at the expectations page and submit your interest via this form by Mar 14, 2025.

Partners are also encouraged to read this quick reference guide to get more information on the overall vision of app bundles from Marketplace.

We identified an error in the data display for Free Apps. Specifically, the maintenance start date was inaccurately updated to reflect the most recent changes in the license, which was not the accurate representation of the maintenance start date.

The issue has now been corrected, and therefore changes will be deployed on 3rd March 2025, impacting 1,039,402 records across Partners.

Partners can access the correct data by checking maintenanceStartDate in the license report APIs using the showLifeTimeFreeLicenses filter across:

1. https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses?showLifeTimeFreeLicenses=true - Get life time free apps licenses data

2. https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses/async/export?showLifeTimeFreeLicenses=true - Initiate async export of life time free apps licenses data

3. https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses/export?showLifeTimeFreeLicenses=true - Export life time free apps licenses data

This announcement is for our upcoming security process & policy changes affecting Marketplace Partners going live in June 2025.

We intend to formally announce these changes to partners on: Feb 27, 2025

• Internal Enablement:https://hello.atlassian.net/wiki/spaces/ENTMRK/pages/4583500027/Pegasus+Enablement

• Partner Portal Draft: https://hello.atlassian.net/wiki/spaces/ENTMRK/pages/4859674279/Pegasus+Partner+Portal+Blog

This initial announcement is intended to make partners aware of the changes coming in June, as well as provide the resources on DAC with specifics around what questions they will be required to answer in our updated App Onboarding and App Review processes.

This changelog ticket is just for our announcement and new/updated DAC pages. NO API or technical changes.

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.