Changelog

We’re announcing the deprecation of the V2 Applications APIs on Atlassian Marketplace.

What’s changing

• The Applications APIs are now deprecated.

• A six-month deprecation window begins immediately, and these APIs will be removed after May 6, 2026.

• Refer to the updated documentation for V3 Parent software APIs to plan your transition.

What you need to do
Partners and developers should migrate to the V3 Parent software APIs to ensure continued functionality and support.

What’s changing?
Partners have consistently requested comprehensive order history for entitlements to better track cloud subscription state changes over time.

To this end, Marketplace team is introducing a new query parameter, showLicensesHistory, to the Licenses API.
When set to true, this parameter enables partners to retrieve historical events - snapshots of licenses.
The response body for historical events remains unchanged, except for the addition of a new field: recordCreatedDate, which indicates when each snapshot was created.

On setting showLicensesHistory: true on Nov 12, 2025 for these licenses,

1. ENT -1 : Displays 2 Snapshot Data with respective recordCreatedDate

2. ENT -2: Displays 1 snapshot Data with respective recordCreatedDate

Benefits:

• Partners can now proactively track subscription lifecycle events

• Reduce support tickets related to license state inquiries

Availability:
This feature is targeted for release on 3rd November 2025.

Next steps:
Partners are encouraged to review and integrate the new reporting capability to access license history snapshots.

Atlassian is revising the timeline for upcoming Marketplace revenue share rate increases, originally scheduled to take effect on January 1, 2026. The new effective date for these changes is April 1, 2026, with subsequent increases adjusted accordingly.

Learn more

We’re announcing the deprecation of the V2 Privacy and Security APIs on Atlassian Marketplace.

What’s changing

• The V2 Privacy and Security APIs are now deprecated.

• A six-month deprecation window begins immediately, and these APIs will be removed after April 30, 2026.

• Refer to the updated documentation for V3 Privacy and Security APIs to plan your transition.

What you need to do
Partners and developers should migrate to the V3 Privacy and Security APIs to ensure continued functionality and support.

Following its review release, we are excited to announce that the V3 Privacy and Security APIs are now generally available on the Atlassian Marketplace. This means these APIs are now fully operational and can be used in production environments.

For more information, see V3 Privacy and Security API documentation.

To prepare for the migration of Free apps to the new Billing system, we are updating Entitlement ID, Entitlement Number and Start Date of free Cloud app licenses—similar to what’s already in place for Cloud Paid Entitlements.

This update is a foundational step to enable the migration of free Cloud app licenses to the new Billing system, ensuring consistency and future scalability.

Note:
Licenses are not being migrated to the new billing system yet. The migration is scheduled for the first week of November 2025.

Data Field Updates

The change is estimated for 250k+ free Cloud app licenses spread across Marketplace Partners. Entitlement ID values and Entitlement numbers will be updated for the the following APIs that provide license details:

• Get transactions

• Export transactions

• Get licenses

• Export licenses

Partners can fetch the updated appEntitlementId and appEntitlementNumber using the lastUpdated field.

1. Do a one-time export of all free Cloud app licenses (licenseType == Free) before the migration (by Oct 31, 2025)

   • Include: appEntitlementId, appEntitlementNumber, maintenanceStartDate, addonKey, cloudID, parentProductName.

2. After the update, map the new appEntitlementId to the UUID using unique identifiers (addonKey, cloudID, parentProductName) to obtain the new appEntitlementId and new maintenanceStartDate.

If you have questions or need more details, please contact us through ECO-HELP tickets.

We’re announcing the deprecation of the V2 Reviews APIs on the Atlassian Marketplace.

What’s changing

• The V2 Reviews APIs are now deprecated.

• A six-month deprecation window begins immediately, and this API will be removed on April 23, 2026.

• Review the latest V3 Reviews APIs for more details.

What you need to do
Partners and developers should migrate to the V3 Reviews APIs to ensure continued functionality and support.

Following its review release, we are excited to announce that the Marketplace V3 Review APIs are now generally available. This means that these reporting APIs are now fully operational and can begin utilizing these APIs in production environments.

For more information, see V3 Review APIS.

We are excited to announce that the Marketplace V3 Parent software APIs are now generally available. This means that these parent software APIs are now fully operational and you can begin utilizing these APIs in production environments.

For more information, see V3 Parent software APIS.

Effective 13 October, Marketplace Partners with qualifying Runs on Atlassian apps can now take home 100% of Marketplace revenue—up to $1 million in lifetime Forge earnings.

• Early access: The revenue share incentive, previously announced for 2026, is now live for Runs on Atlassian apps. Partners keep 100% of revenue until reaching $1M in lifetime Forge revenue.

• Automatic application: If your Runs on Atlassian apps are listed and your total Forge revenue is under $1M, no action is needed. The incentive will be reflected in your next payout.

• New launches qualify: Apps launched after October 13, 2025, are also eligible for this incentive.

• To help partners track total earnings, a new LIFETIME_GMV field in the metricFields Array will be made available in the Marketplace reporting API on October 13, 2025.

• This field reports the lifetime Gross Merchandise Value (GMV) for non-Harmonized Forge app versions.

• Partners are requested to review the updated API documentation and familiarize with the new LIFETIME_GMV field starting Monday, October 13.

• For additional details and context, visit the Atlassian blog announcement.

To help Marketplace partners distinguish between Commercial and AGC-compatible (Atlassian Government Cloud) apps, we have introduced a new API field: cloudComplianceBoundaries across Marketplace APIs.

The valid values for the API field are as follows:

• commercial: The standard commercial version of the app.

• fedramp_moderate: The AGC-compatible version of the app.

The new field is available in the following Marketplace APIs:

• Apps -> https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-group-apps

• App versions -> https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-app-versions/#api-group-app-versions

• Reporting → The new field will be added to license and transaction reports to help partners differentiate AGC licenses and transactions from Commercial Cloud licenses and transactions.
  https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-group-reporting

  • Licenses

  • Export Licenses

  • Initiate Async Export licenses

  • Transactions

  • Export transactions

  • Initiate Aysnc Export Transactions

• Partners are requested to review the latest API documentation for more details.

• Note: AGC-compatible apps are not yet enabled for general availability (GA) to customers and therefore, Partners will not see any AGC licenses or transactions at this time.

More details on GA date for customers will be shared via QRG separately. For any questions, please raise an ECO-HELP ticket.

We are excited to announce the release of a comprehensive new guide for Marketplace Partners on how to publish and market apps for Atlassian Government Cloud (AGC). This introduces a step-by-step process for listing AGC-compatible apps,
https://developer.atlassian.com/platform/marketplace/publish-and-list-agc-apps/

Key Updates:

1. New Documentation Available

   1. Required steps to publish AGC-Compatible app

   2. How to create and submit an AGC app version via the Marketplace Partner Portal

   3. Guidance on updating AGC-specific app details and leveraging content from your commercial cloud version

2. Pricing and Licensing for AGC Apps

   • Partners can set and upload pricing specifically for AGC-Compatible app

3. Support and Resources

   • Additional resources:

     • https://developer.atlassian.com/platform/framework/agc/guides/build-agc-compatible-forge-apps/

     • https://developer.atlassian.com/platform/framework/agc/

Action Required:

• Review the new guide and update your app listings and processes as needed. Please raise an ECO-HELP ticket in case you have any queries.

• Marketplace Reporting: We will share how to identify Atlassian Government Cloud licenses and transactions via Changelog on Friday, 3rd October.

We are adding two new Mandatory Privacy & Security tab questions.

1. “App accesses Atlassian Personal Access Tokens (PATs), user account passwords, or another type of shared secret”
   This question requires you to specify whether or not your app currently utilizes PATs (Personal Access Token) or another shared secret to function. More about PAT sharing policy. This ensures the response is being disclosed to customers for the small number of partner apps that still utilize PATs.

2. “Provide a reason/justification for the permissions that are required by your app.”
   This question requires you to specify a justification for the scopes requested by your app. This enables customers to have a better understanding of the reasoning for your app scopes when viewing the Privacy & Security tab details.
   :info: Note: The Permissions Justification field appears only if your app has at least one requested scope.

We are introducing Entitlement Numbers to Data Center (DC) licenses, aligning them with Cloud Entitlements as previously announced (https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-2798). To implement this, our internal data pipelines will be updated, specifically the appEntitlementId and appEntitlementNumber fields.

A 24-hour maintenance window is required to ensure 100% accuracy of data field updates to current paid Data Center licenses.
Maintenance window: 1:30am UTC, 25 September 2025 – 1:30am UTC, 26 September 2025.

During this period:

• Marketplace Reports will not reflect updates to current DC licenses, transactions or new Data Center licenses.

• Customers will be able to create transactions, create new licenses.

After the update, Marketplace reports will be backfilled on 26 September 2025 to accurately display DC license and transactions data.

Why this matters:

• This change lays the groundwork for future migration of Data Center licenses to the new billing system and Marketplace needs to ensure accurate Entitlement data is updated for Marketplace customers & Partners.

• Note: Licenses are not being migrated to the new billing system at this stage.

For detailed explanation of the changes, partners are requested to check our previous communication: https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-2798 .
For questions or further details, please contact us via ECO-HELP tickets.

While version 3 of the Marketplace App Migration APIs is still under development, we’re releasing the documentation for these Marketplace App Migration APIs early to help you prepare for the upcoming changes. This release includes a preview of the API documentation schema and examples of API requests and responses.

To ensure smooth transition with the upcoming changes, we recommend to review the API documentation to understand and prepare for the upcoming changes.