This changelog is the source of truth for all changes to the Marketplace that affect people publishing apps.
Posts are made in the Marketplace announcements category of the developer community when the changelog is updated. Subscribe to the Marketplace announcements category to get notifications.
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.
Here are some helpful suggestions for you to consider:
Transition planning: Based on this documentation, it may be helpful to assess the bandwidth required for these changes and incorporate them into your roadmaps. Reviewing this documentation could provide a clearer understanding of the new APIs and help you accurately estimate the efforts involved in the transition.
Project planning: Consider preparing your execution plans and project plans so that you’re ready to hit the ground running once the APIs become available.
Staying informed: Keeping an eye out for upcoming communications from the Marketplace team can help you stay updated on timelines. Look out for updates via changelogs, enhancements to the quick reference guide on the Partner Portal, DAC, and other channels.
What’s changing?
To help initiate Atlassian’s migration of Data Center licenses to the new Billing system, we are introducing Entitlement Numbers to Data Center (DC) licenses—similar to Cloud Entitlements.
Note: Licenses are not being migrated to the new billing system yet.
Data Field Updates
Identifier Type | Before Change | After Change |
|---|---|---|
| SEN-1234567 | SEN-1234567 |
| Null | 123e4567-e89b-12d3-a456-test |
| Null | ENT-123-ABC-123-ABC |
The change is estimated for 200K+ Data Center licenses spread across Marketplace Partners. Entitlement ID values and Entitlement numbers will be updated for the the following APIs that provide Data Center license details:
Partners can fetch the Updated appEntitlementId & appEntitlementNumber using the lastUpdated field.
Why are we doing this?
The change will help lay the foundation for future migration of Data Center licenses to the new Billing system.
Further communications on migration dates/ cohorts will be provided in QRG and Change-logs.
If you have questions or need more details, please contact us through ECO-HELP tickets.
:info: Please note: We initially planned to go live on 19 September 2025; however, due to a deployment issue, we now aim for the coming week. We will provide an update via the Changelog before the changes go live.
We've rolled back the Developer Spaces feature for Forge apps in the Developer console and Marketplace. We're taking this step to gather more feedback and improve the experience before making it generally available again.
If you started using Developer Spaces, your apps and team settings will revert to the previous experience. If you made changes to your team structure or roles during this period, review your team setup and adjust as needed to match the previous configuration.
We'll share updates and a new release date soon. To provide feedback or learn more, see the original September 3, 2025, changelog or the Community.
These changes have been rolled back. For more details, please see https://developer.atlassian.com/changelog/#CHANGE-2781.
We've launched Developer Spaces in the Developer console for Forge apps, providing a new way to organize your apps, team members, and billing in one place. All new Forge apps must now be created in a Developer Space, and existing non-marketplace apps must be linked to a space.
This release includes:
Admin role management: All members are space admins with full permissions to manage apps and team membership.
Developer Console integration: Manage spaces, apps, and team members, and use the space switcher to navigate between spaces.
App assignment and management: Assign existing non-marketplace apps to the appropriate developer space in the console. Marketplace apps are already linked to the developer space matching the marketplace partner account name.
CLI support: Updating the CLI to version 12.5.0, you can create Developer Spaces and assign apps via the Forge CLI during forge create or forge register workflows. Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
App transfer (manual process): Transferring apps between spaces requires a support ticket for non-marketplace apps or following the Marketplace transfer process for Marketplace apps.
Important changes to Marketplace publishing
Publishing apps to the Marketplace will now work differently, and it’s important to review these updates:
The list of publishable Forge apps is now based on Developer Space membership.
All Forge apps must be linked to a Developer Space before they can be published to the Marketplace.
Only Developer Space members with the appropriate permissions can publish apps.
These changes align publishing and billing responsibilities with Developer Space governance and prepare for the upcoming usage-based pricing model.
If you publish apps to the Marketplace, review your current apps and confirm they are linked to the correct Developer Space.
Known limitations:
Only the Admin role is available for this release. Additional roles and permissions will be introduced in the future. For anyone interested in more roles, please see the Jira ticket for feedback : https://ecosystem.atlassian.net/browse/FRGE-1893
App transfer between Developer Spaces requires manual intervention.
Some advanced governance and reporting features are not yet available.
For more information, see the Developer Space documentation.
While version 3 of the Marketplace privacy and security APIs is still under development, we’re releasing the documentation for these Marketplace app software 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.
Here are some helpful suggestions for you to consider:
Transition planning: Based on this documentation, it may be helpful to assess the bandwidth required for these changes and incorporate them into your roadmaps. Reviewing this documentation could provide a clearer understanding of the new APIs and help you accurately estimate the efforts involved in the transition.
Project planning: Consider preparing your execution plans and project plans so that you’re ready to hit the ground running once the APIs become available.
Staying informed: Keeping an eye out for upcoming communications from the Marketplace team can help you stay updated on timelines. Look out for updates via changelogs, enhancements to the quick reference guide on the Partner Portal, DAC, and other channels.
As mentioned in our previous changelog regarding the vendor details APIs served by Atlassian Marketplace, we have now removed these APIs. Consequently, partners will no longer be able to access them.
Guide to replacing vendor APIs with developer space APIs
Vendor API | Replacement API |
|---|---|
Add vendor contact | |
Delete vendor contact | |
Update vendor contact | |
Get vendor contacts | |
Get vendor contact | |
Get vendor | |
Update vendor | No replacement |
Get all vendors | No replacement |
Create vendor | No replacement |
Get payment details | No replacement |
Create/update payment details | No replacement |
License import API | No replacement |
For more information, see the Marketplace Partners: Changes to Vendor Detail APIs - Quick Reference Guide
The access pattern has been changed to developerId, which is a unique identifier for a developer space.
Here is the API which will give the mapping of vendorId to developerId
Below is the mapping of vendor attributes to developer space attributes
Vendor attribute | Developer space attribute & API to access the attribute |
|---|---|
Vendor Id | Developer ID (API) |
Name | Name (API) |
Vendor’s listing attributes (e.g. email, phone, address, etc) | Developer space’s listing attributes (API) |
Vendor contact’s permissions | Developer space member’s roles (API) |
Vendor contact’s roles | Developer space member’s categories (API) |
We've simplified user access management with predefined roles. Admins can now easily assign granular access levels to team members using these curated roles.
These new Developer Space member roles replace the previous Vendor Contact permissions. Details about these roles and their corresponding permissions are available in the previously published RFC.
We are releasing the following Marketplace version 3 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.
Here are some helpful suggestions for you to consider:
Transition planning: Based on this documentation, it may be helpful to assess the bandwidth required for these changes and incorporate them into your roadmaps. Reviewing this documentation could provide a clearer understanding of the new APIs and help you accurately estimate the efforts involved in the transition.
Project planning: Consider preparing your execution plans and project plans so that you’re ready to hit the ground running once the APIs become available.
Staying informed: Keeping an eye out for upcoming communications from the Marketplace team can help you stay updated on timelines. Look out for updates via changelogs, enhancements to the quick reference guide on the Partner Portal, DAC, and other channels.
We have identified an issue where, for a given transaction, the customer contact information provided in the Transactions API, customerDetails field:
Billing contact name
Billing contact email
Technical contact name
Technical contact email
was not correctly displayed on the Transactions API and Marketplace Transactions reports.
The issue has now been fixed for future transactions, and approximately 30,000 transactions have been back-filled to display the accurate customer contact information, depending on customer preference.
Next Steps:
These changes will go live in production starting on Aug 19, 2025 and can be accessed via the following APIs:
Partners can fetch this data through the lastUpdated field of the API.
Please note: We initially planned to go live on 18 August 2025; however, due to a deployment issue, we will now launch on 19 August 2025.
We identified an issue regarding the reporting data for licenses in new billing system for Cloud Apps. The maintenance end date was not updated when a subscription was cancelled. When a customer cancelled their subscription, the maintenance end date for their entitlement was not updated to reflect the actual cancellation date. This led to inaccurate entitlement periods.
Resolution:
The issue has now been fixed and will be deployed on Aug 19, 2025
This fix affects approximately 60,000 licenses across Marketplace partners, including 1200+ active licenses.
Moving forward, maintenance end dates will correctly update to match the cancellation date for all affected Cloud App subscriptions.
Next Steps:
Partners can fetch updated license data using the lastUpdated field in the licenses API.
Please note: We initially planned to go live on 18 August 2025; however, due to a deployment issue, we will now launch on 19 August 2025.
While version 3 of the Marketplace app software APIs is still under development, we’re releasing the documentation for these Marketplace app software 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.
Here are some helpful suggestions for you to consider:
Transition planning: Based on this documentation, it may be helpful to assess the bandwidth required for these changes and incorporate them into your roadmaps. Reviewing this documentation could provide a clearer understanding of the new APIs and help you accurately estimate the efforts involved in the transition.
Project planning: Consider preparing your execution plans and project plans so that you’re ready to hit the ground running once the APIs become available.
Staying informed: Keeping an eye out for upcoming communications from the Marketplace team can help you stay updated on timelines. Look out for updates via changelogs, enhancements to the quick reference guide on the Partner Portal, DAC, and other channels.
As previously announced in the https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-2623 and https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/858980395/Marketplace+Partners+Maximum+Quantity+Billing+-+Quick+Reference+Guide, we’re introducing maximum quantity billing (MQB) in a phased approach.
Maximum Quantity Billing(MQB) charges will appear in Transactions Reports and following APIs.
Transactions API: Get transactions
Export Transactions: Export transactions
Async Export Transactions Initiate Async Export transactions
To help identify MQB transactions, in the transactions API response, purchaseDetails section,
proratedDetails returns an array of objects, each with:
addedUsers: Number of additional users added during the monthly billing cycle.
date: Date when additional users were added.
This helps partners track user additions and calculate prorated charges for each user additions during the billing cycle.
In addition, to view all MQB charges, a separate filter view
showProratedTransactions returns list of all MQB charges and is labeled as sales price(prorated) in Transaction Reports.
To ensure smooth transition with the upcoming changes, we recommend partners to review the API documentation as well as the Quick Reference Guide for an example transaction.
We have identified an issue due to which the EXPERT discount information was not provided on the Transactions API and Marketplace Transactions reports for certain entitlements from the new billing system.
As a result, solution partner discounts were not displayed for certain entitlements and their respective order IDs.
The issue has now been fixed, and transactions have been back-filled to display the accurate Discount Amount in the purchaseDetails.discounts array field and type EXPERT for 44,000 transaction line-items spread across partners.
Next Steps:
The changes will go live in production starting on Aug 5, 2025 and can be accessed via the following APIs:
Partners can fetch this data through the lastUpdated field of the API.
We've updated the payment method for US-based bank accounts of Marketplace Partners from Wire to ACH (Automated Clearing House) transfers.
In July 2025, our Accounts Payable Team will perform a penny test payment of $1 via ACH to the routing number you provided in the Marketplace portal to verify its accuracy. If your current routing number does not accept ACH payments, the test payment will be returned to us.
Marketplace Partners will be notified if any updates are required. We recommend reviewing your banking information in the Marketplace Portal to ensure it supports ACH payments.
ACH transfers typically take 1-3 business days to reflect in your bank account. You may notice payments appearing around 3 days later than usual, similar to current processing times, unless affected by holidays, weekends, or payment issues.
If you have any questions or need assistance updating your banking details, contact us through the AP Service Desk.
Atlassian previously announced that customer general availability (GA) for multi-instance pricing would move to the fourth quarter of 2025. We are pleased to share that, while GA is still planned for Q4, we have launched a closed Early Access Program (EAP) with customers. This EAP will help us ensure we deliver a high-quality, robust feature.
In order to help Marketplace Partners accommodate larger customers, Marketplace cloud app pricing will be adjusted to match parent product pricing. We increased the number of users that customers can license on Jira Cloud from 50,000 to 100,000 on Jun 26, 2025
Beginning Jul 9, 2025, the pricing tiers for Jira cloud apps will be increased up to 100,000 users, a 100% increase from the previous limit of 50,000 users, with the following new pricing tiers added: 50,001 - 60,000 60,001 - 70,000 70,001-80,000 80,001-90,000 90,001-100,000 .
Rate this page: