Changelog

We are deprecating v2 App pricing APIs (Get pricing API & Submit pricing API) and providing replacement for those APIs via APIs powered by Atlassian Commerce platform.

This document will guide you on how to use the new Commerce APIs.

Currently, Marketplace Partners can set app pricing in two ways: either through the Marketplace Partner Console UI or by using the Marketplace v2 APIs. However, the Marketplace API only supports managing pricing for the Standard edition of apps.

In the future, partners will continue to have two options for setting pricing: the Marketplace UI or a new API provided via the Commerce. The Commerce API will offer enhanced capabilities, allowing partners to manage pricing for different editions, multi-instance apps, and handle Atlassian Government Cloud (AGC) & Isolated Cloud-related packaging and pricing requirements.

We’re deprecating below Marketplace v2 pricing APIs:

• GET /addons/{addonKey}/pricing/{cloudOrServer}/{liveOrPending}

• PUT /addons/{addonKey}/pricing/{cloudOrServer}/{liveOrPending}

Deprecation schedule

• Deprecation announcement date: Dec 10, 2025

• End of support date: Jun 30, 2026

• Removal or behavior change date: Jun 30, 2026

After the removal date

• Calls to the v2 pricing APIs will return error with status 410 (Gone)

What you need to do

• Stop using the v2 Pricing APIs.

• Use the Commerce Pricing APIs described in this guide to:

  • Update App Pricing

  • Fetch App Pricing across editions and offerings.

Here is the list of app pricing APIs with consolidated decision

This is for Marketplace Partner who want to use APIs to Update or Fetch Pricing of their apps

https://developer.atlassian.com/platform/marketplace/marketplace-app-pricing-api/

Following the Preview release, the Forge Automation Actions is now generally available. The Automation action module allows you to extend the Automation Platform and add new Forge-based actions to your app. With this release Forge Actions can now output smart values, enabling seamless data flow and dynamic automation.

For more information, see the Forge Automation Action module documentation.

What’s Fixed?

We recently discovered an issue in the Transactions API that affected 2,166 paid transactions spread across Marketplace Partners. In these cases, Marketplace Promotion discounts—including their values and codes—were not displayed. This issue was limited to transactions processed through the new billing system for Cloud Apps and only impacted a small subset of transactions that included multiple discounts.

Data fields

This issue has now been resolved. Partners can now retrieve updated transaction details, including the applied Marketplace Promotion codes, by using the purchaseDetails.Discounts array with TYPE: MARKETPLACE_PROMOTION in the Transactions API.

Moving forward, transactions with Marketplace promotions will correctly display the associated discount amounts.

Next Steps:
Partners can fetch updated transactions data using the lastUpdated field in the Transactions API.

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

What’s changing

• The Reporting APIs are now deprecated.

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

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

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

What’s new:

• Multi Year Billed Annual allows customers to commit to multi-year Marketplace App subscriptions with annual billing, instead of paying the full term upfront. This aligns with Atlassian’s parent product billing and meets enterprise customer demand for flexibility and predictability.

Key points detailing the MYBA transactions is covered in the attached QRG

Action required:
No action needed from partners at this time. Reporting enhancements are planned for Q1 CY 2026.

Link to the Quick Reference Guide is provided here: https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/1109983239/Marketplace+Partners+Multi-Year+Billed+Annual+MYBA+Quick+Reference+Guide

We’re announcing the deprecation of the V2 App versions, Apps and Assets APIs on Atlassian Marketplace except for these APIs-

1. Get apps - https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-get

2. Get app pricing - https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-pricing-cloudorserver-liveorpending-get

3. Submit app pricing - https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-pricing-cloudorserver-liveorpending-put

What’s changing

• The V2 App Versions , V2 Apps , V2 Assets are now deprecated.

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

• For the APIs that are excluded in the current deprecation notice , we will send another change-log with their replacement details in the upcoming days.

What you need to do Partners and developers should migrate to the V3 APIs to ensure continued functionality and support. Refer to the updated documentation for V3 App listing , V3 App Software , V3 App Version Listing , V3 Assets APIs to plan your transition. For more details on the migration process from V2 to V3 APIs, please refer to this Quick Reference Guide (QRG): https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/735608891/Marketplace+Platform+Changes+GA+and+Partner+Implications+-+Quick+Reference+Guide . For the final API endpoints and response structures, please refer to the latest documentation present on DAC. We appreciate your cooperation and look forward to ushering in a more streamlined and efficient Atlassian Marketplace experience. Thank you for your continued support.

We are enhancing the security of access tokens used for private app listings in the Atlassian Marketplace.

Key Updates -

Increased Token Length

• Previous: 8-character tokens (e.g., a1ccc3d4)

• New: 36-character tokens (e.g., 524e8400-e29b-41d4-a716-456755440000)

This change will be applied automatically to all new tokens generated after Nov 20, 2025

✅ Existing Tokens - Previously generated tokens will continue to work and remain valid. However, we recommend regenerating tokens for enhanced security.

✅ Integration Impact - If you have automated systems that parse or validate token format, please ensure they can accommodate the new 36-character format.

Upcoming -

✅ Token Display - Tokens will appear masked on the Marketplace Partner Portal. Simply click to reveal the full token when you need to use it.

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

What’s changing • The V2 App Migrations APIs are now deprecated. • A six-month deprecation window begins immediately, and these APIs will be removed after May 31, 2026 .
• Refer to the updated documentation for V3 App Migration APIs to plan your transition.

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

Multi-instance pricing is now live, enabling Cloud Enterprise customers to be charged based on the number of unique users of an app across multiple instances, regardless of the number of product instances.

• 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.

• 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.

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

Partners, if you have not already set your multi-instance pricing, then we recommend that you update it as soon as possible.

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

For more information, see V3 App migration APIs .

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

For more information, see V3 App software APIs and V3 Asset APIs.

Date: 2025-11-10

We recently identified an issue affecting approximately 30,000 Cloud license records on the Free starter tier. Following the migration from the old billing system to the new billing system, these licenses (entitlements), distributed across multiple marketplace partners, were incorrectly marked as churned.

We have now corrected these records in the licenses API, ensuring that their status accurately reflects the following:

• licenseType: Free

In addition, the corresponding churn data, shared via cloud churn API has been updated to reflect these changes.

This fix is part of ongoing improvements to support the migration of Cloud licenses to the new Billing system. The update ensures that license status data is accurate.
Action for Partners:
Partners can retrieve the updated data using the lastUpdated field in the Licenses API.

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

For more information, see V3 App listing APIs and V3 App version listing APIs

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 31, 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.