Changelog

We've added a new field product_id to the CSV file returned by the Get latest product catalog snapshot v3 API. All the existing fields are untouched and they remain as-is. For more details, please refer to the documentation of the aforementioned API.

A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-124-evolving-the-marketplace-trust-program/98418

We identified an issue in the Transactions and Licenses APIs where the hostEntitlementNumber and hostLicenseId fields were incorrectly mapped to Customer Service Management (CSM) (part of Service Collection SKU) instead of the underlying Atlassian Apps (Jira or Jira Service Management).

This issue affected approximately 8K entitlements across partners and has now been fixed as of Jan 15, 2026.

• hostEntitlementNumber and correspondly hostLicenseId will no longer map to Customer Service Management.

• The app entitlements now map to the corresponding Jira products:

  • Jira Service Management (JSM), or

  • Jira.

• No entitlements were removed; only the host entitlement has been updated.

Partners can use the lastUpdated field to identify updated licenses and transactions via:

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

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

We’ve updated how Data Center promotion are paginated in the Get promotions paged API so they behave consistently with Cloud promotion.

What changed

Previously, partners used the limit , totalItems and offset fields to navigate Data Center and Server promotion via: https://developer.atlassian.com/platform/marketplace/rest/v1/api-group-promotions/#api-group-promotions

As part of the ongoing DC promotion migration( https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-2986):

• Data Center promotion codes

  • Now use cursor-based pagination via the nextId and prevId fields returned by the API response.

  • This is aligned with how Cloud promotions are already paginated.

  • Partners are requested to use the nextId and prevId values to navigate forward and backward through pages of Data Center promotion codes.

• Server promotion codes

  • No change. Server promotion continue to use limit, totalItems and offset for pagination.

  • You can keep using your existing integration for Server-only use cases.

For full API details, see the Promotions API docs below, while Changes to Developer documents will be updated by Jan 23, 2026
https://developer.atlassian.com/platform/marketplace/rest/v1/api-group-promotions/#api-group-promotions

We’re removing the legacy “Current categories” field from the Partner Portal effective Jan 15, 2026

What’s changing

• The “Current categories” section will be removed from the App details page in the Vendor Portal.

• As communicated previously (Marketplace changelog), this field no longer impacts how apps are categorized or displayed on the Marketplace and is now being fully phased out.

• There are no changes to the Categories or Keywords fields. These fields continue to power app categorization, navigation, and discovery on the Marketplace.

More details
For more information on the app categorization system, please refer to:
https://developer.atlassian.com/platform/marketplace/new-app-categorization-system-in-marketplace/

We’re announcing the deprecation of the V2 Get apps https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-get on Atlassian Marketplace.

What’s changing

• The V2 Get apps api is now deprecated.

• Deprecation window begins immediately, and these APIs will be removed after June 30, 2026 .

What you need to do Partners and developers should migrate to the V3 API to ensure continued functionality and support. Refer to the updated documentation for V3 Get Product Catalog Snapshot API 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.

To help our Marketplace Partners build more secure applications and streamline the app approval process, we are open-sourcing the security ruleset used by our internal marketplace-sast-scanner.

Earlier this year, we introduced mandatory SAST (Static Application Security Testing) scanning for Data Center apps as part of our Security Requirements. Since then, we’ve heard valuable feedback from our partner community regarding transparency into the automated security testing to help you identify and fix vulnerabilities before you submit your apps to the Marketplace.

By making these rules public, we aim to:

• Support Shift-left Security practices: Empower you to run the same checks locally that our Ecoscanner platform runs

• Foster collaboration: Allow community to contribute to the ruleset, helping the entire ecosystem stay ahead of emerging threats

The ruleset is built for Semgrep and is now available on GitHub. You can integrate these rules into your local development environment or CI/CD pipelines today.

Key resources:

• Ruleset Repository: atlassian-labs/atlassian-sast-ruleset

• Documentation: SAST Scanner for Data Center apps

• Support: If you have questions about specific scan results, please reach out via the Partner Support Portal

We are migrating marketplace promotion codes from the legacy billing system to our new billing system. This migration aligns Data Center promotion processing more closely with how we handle cloud promotion codes today, and helps ensure data consistency and integrity across systems.

During the migration window, only redeemed inactive promotion codes will:

• Not appear in the Partner Portal UI

• Not be returned by the Promotions API:
  GET /marketplace/catalog/partners/{partnerId}/promotions/paged
  (see docs: https://developer.atlassian.com/platform/marketplace/rest/v1/api-group-promotions/#api-marketplace-catalog-partners-partnerid-promotions-paged-get))

We require a short, controlled window to safely migrate promotion code data, ensuring data integrity and consistency across systems.

Promotion codes will be processed by the new billing system similar to cloud promotion codes going forward.

• If you rely on historical redeemed inactive promotion codes, Export or record any needed data (bundled or standalone) via:

  • Partner Portal UI, or

  • Promotions API: https://developer.atlassian.com/platform/marketplace/rest/v1/api-group-promotions/#api-marketplace-catalog-partners-partnerid-promotions-paged-get

• If you need redeemed inactive promotion data or Bundled promotion code during the migration window(5 Jan - 29 Jan 2026), please raise an ECO-HELP ticket and we can retrieve it for you.

• Redeemed inactive promotion codes will be backfilled and visible again in both:

  • the Partner Portal UI, and

  • the Promotions API byJan 29, 2026 .

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

What’s changing

• The V2 Get categories , V2 Get category are now deprecated.

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

What you need to do

Partners and developers should migrate to the new APIs to ensure continued functionality and support. Refer to the updated documentation for Get Product Tags , Get product tag 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’re announcing the deprecation of the V2 Licenses APIs on Atlassian Marketplace.

What’s changing

• The V2 Get License Type , V2 Get License Types are now deprecated.

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

What you need to do

This is a static list. You can get the valid license types from the response body of - V3 Get app software version by build number

Partners and developers should migrate to the V3 APIs to ensure continued functionality and support.

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