Changelog

In reference to https://developer.atlassian.com/platform/forge/changelog/#CHANGE-2876, we introduced a new state—Legacy free licensing—for:

Apps past their subscription or trial end have moved to a legacy “free� licensing state. These inactive installations remain unaffected by the new uninstall flow until an admin initiates uninstall.

For a time, these licenses appeared as FREE ACTIVE licenses on the Marketplace Reporting portal and API responses. (See https://jira.atlassian.com/browse/MP-556 )

We are adding a new license type, Legacy Free to signify those licenses, to API endpoints and the Reporting UI. It will be available from May 20, 2026.

For example, when viewing a specific app’s license:

• Licenses API

  • Field - licenseType

  • Query Parameter - licenseType: legacy_free

  • GET /vendors/{vendorId}/reporting/licenses https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-get

  • GET /vendors/{vendorId}/reporting/licenses/export https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-export-get

  • POST /vendors/{vendorId}/reporting/licenses/async/exporthttps://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-async-export-post

• Transactions API

  • Field - purchaseDetails.licenseType

  • GET /vendors/{vendorId}/reporting/sales/transactions https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-sales-transactions-get

  • GET /vendors/{vendorId}/reporting/sales/transactions/exporthttps://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-sales-transactions-export-get

  • POST /vendors/{vendorId}/reporting/sales/transactions/async/exporthttps://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-sales-transactions-async-export-post

• Licenses in Marketplace Reporting Portal

  • Filter - License Type: Legacy Free

  • License Type will be shown as Legacy Free

  •  

     

We are transitioning the Atlassian Marketplace rating scale from 1–4 stars to 1–5 stars. This change applies to all listed Marketplace apps — free and paid — across the Marketplace website and embedded experiences in Jira and Confluence.

Moving to a 5-star scale aligns the Atlassian Marketplace with industry-standard rating systems, giving customers a more intuitive, granular way to evaluate and compare apps.

What’s changing

• Your app’s overall aggregate rating will now be displayed on a 5-star scale.

• A linear conversion maps existing ratings to the new scale:

• Historical reviews will keep their original star ratings on the reviews tab. For example, a review originally submitted as 3/4 stars remains displayed as 3/4. Only the aggregate app rating is shown on the new 5-star scale.

• New reviews submitted after today’s date May 20, 2026 will use the 5-star scale by default.

• Customers can edit previous reviews. Users who previously rated an app will see a tooltip when editing their review explaining the scale conversion and allowing them to update their rating if they choose. This tooltip only appears when a customer actively edits a review — it won’t surface unprompted.

• Data Center apps: Marketplace web surfaces will display ratings on the 5-star scale for Data Center apps. The Universal Plugin Manager (UPM) within Data Center products will continue to show ratings on the 1–4 scale.

API changes

The averageStars and stars fields in Marketplace public APIs now reflect the 5-star scale. A new boolean field, transitionedToFiveStarRating, has been added to individual review objects to indicate which scale was used.

Affected endpoints:

• rest/2/addons

  rest/2/addons/vendor/{vendorId}

  rest/2/addons/{addonKey}

  • reviews.averageStars → 1–5 scale

• rest/2/addons/{addonKey}/reviews

  rest/2/addons/{addonKey}/reviews/id/{reviewId}

  rest/2/addons/{addonKey}/reviews/mine

  • stars → 1–5 scale

  • transitionedToFiveStarRating → true if the review was submitted on the 5-star scale; false if it originated on the 4-star scale

• rest/3/products/{productId}/reviews

  rest/3/products/{productId}/reviews/{reviewId}

  • Same behavior as above for stars and transitionedToFiveStarRating

Sample API response:

Action required

For most partners, no action is required — Atlassian handles the migration automatically.

However, if you consume rating data via Marketplace APIs, you should:

1. Update integrations to expect stars and averageStars on a 1–5 scale.

2. Incorporate the transitionedToFiveStarRating flag if your systems distinguish between legacy and new reviews.

Action needed by June 30, 2026: If you have an Atlassian Bug Bounty program, it must be made public to maintain your program status and Marketplace badges.

The good news: you don't need to be fully public by then — you just need to submit an ECOHELP ticket to start the process. Submitting by June 30th protects your program.

Here's what to do:

1. Review the full requirements here

2. Raise an ECOHELP ticket here

Please note:

• Tickets not submitted by June 30th will be automatically closed.

• Submitted tickets that are inactive for 14 days will also be closed.

• Either may result in your program being paused and the removal of associated Marketplace badges.

We're excited to announce that the downloadable product catalog CSV, available via the Marketplace V3 Product Catalog Snapshot APIs, has been enhanced with Total Install Counts.

This new field provides the aggregate number of installations for each app. For more details see: V3-Product Catalog Snapshot API

We are enhancing the partner experience in completing the Marketplace App onboarding security requirements by consolidating all security questionnaires, including both partner and app-specific questions, into a single Forge app. This app is accessible via your Marketplace App Approval requests. You can view your up-to-date questionnaire responses within your existing and future app approval requests. We are also making it easy for you to review the security scanner findings (vulnerabilities) and designate a point of contact for app-specific questions.

Please refer to the QRG for more details: https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/1723105354/Completing+Marketplace+App+Onboarding+Security+Requirements+-+Quick+Reference+Guide

Important Reminder: As part of the ongoing Marketplace platform re-architecture, Marketplace V2 APIs are scheduled for deprecation on June 30, 2026.

You can find the full context, including deprecation timelines, replacement V3 endpoints, and partner enablement details in the Quick Reference Guide here.

A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-133-evolving-the-marketplace-trust-program-follow-up-to-rfc-124-trust-program-requirement-updates-and-validation-steps/100401

When a Marketplace app supports Forge Multiple-App Compatibility, its installation can generate multiple installation links — one for each required and additional compatibility. Beginning Apr 23, 2026, we will consolidate these into a single, unified active installation count: one required link and its associated compatible links will be counted as one installation.

This ensures partners see accurate active install metrics that reflect true unique installations, rather than a count per individual link.

Here's how the installation count will change when viewing a specific app installed on a site:

Note: Existing apps that already support multiple‑app compatibility may experience a slight decrease in their install counts as a result.

• Fetch Metric time series API
  POST /vendors/{vendorId}/partner-metrics with DISTRIBUTIONS as the metricSets
  https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-partner-metrics-post

• Active Installations tab in Manage App page

• Install Counts in App Listing and App Tile

In order to help Marketplace Partners accommodate larger customers, Marketplace cloud app pricing will be adjusted to match parent product pricing

Beginning April 23, 2026, the pricing tiers for Confluence Cloud Marketplace apps will be increased up to 250,000 users, a 67% increase from the previous limit of 150,000 users, with the following new pricing tiers added: 150,001-160,000 160,001-170,000 170,001-180,000 180,001-190,000 190,001-200,000 200,001-210,000 210,001-220,000 220,001-230,000 230,001-240,000 240,001-250,000

As part of enabling these higher tiers, we’ll be putting a temporary pricing hold in place for Marketplace apps from April 20, 2026 at 12:00 pm IST to April 22, 2026 at 11:30 pm IST.

We previously notified partners about these changes on April 6 in this update here.

 

Important Reminder: As part of the ongoing Marketplace platform re-architecture, Marketplace V2 APIs are scheduled for deprecation on June 30, 2026.

You can find the full context, including deprecation timelines, replacement V3 endpoints, and partner enablement details in the Quick Reference Guide here.

We’re deprecating the Cloud Security Participant badge as part of our broader work to evolve the Marketplace Trust program.

Effective March 31, 2026:

• The Cloud Security Participant badge will be retired and removed from the Marketplace.

• We will continue to highlight participation in the Bug Bounty program on app listings for both Cloud and Data Center apps, so customers can still easily see your ongoing security investment.

As we transition to the new Marketplace v3 APIs, the ECOHELP app approval process now comes with new statuses for better visibility:

• approved - Congratulations, your app has been approved and sent for publishing in the backend.

• Published - Your approved app is now available and visible on the Marketplace.

:info: The rejection status awaiting resubmission is applicable for both v2 and v3 APIs and the legacy approval status Closed may still be in use when v2 APIs are triggered.

We introduced an optional legacyListingDetails field to the Marketplace v3 API endpoint:

PUT /rest/3/product-listing/{productId}

Although optional, we strongly recommend using this field in update requests to prevent legacyListingDetails data from being overwritten as null.

As discussed in RFC-124: Evolving the Marketplace Trust Program, we will retire the Cloud Security Participant badge on Mar 31, 2026. We will continue to highlight partners’ investment in the Bug Bounty program on the app listing for both cloud and Data Center apps.

Starting Mar 31, 2026, the Cloud Security Participant badge will be removed from:

• App tiles shown in search results and collection pages

• The top of the app listing page (under Trust Signals), as shown below

• Trust signal filters, as shown below

We’ve introduced an optional legacyListingDetails field to the following Marketplace v3 API endpoints:

• GET /rest/3/product-listing/{productId}

• GET /rest/3/product-listing/developer-space/{developerId}