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.
We are updating the look and feel of the "App details" flows in the partner portal. The functionality of the different components will remain the same and the updates are limited to visual changes only.
Initially, a small percentage of partners will gain access to these updates, with a phased rollout planned for all partners to complete by Feb 14, 2025. For more information, please refer to the Quick Reference Guide(QRG) here.
Permission changes towards the reduction of domain egress of your app are now treated as a a minor update.
For example, while previously triggering major updates, the following external egress permission changes now trigger a minor update:
Updating {"IMAGES":["*"]}
to {"IMAGES":["any list of domains"]}
Updating *.media.atlassian.com
to https://api.media.atlassian.com
As such, we encourage partners to improve the trust posture of their apps by reducing the egress or improving the transparency of the app egress.
These updates can help if you’re looking to make your app eligible for the Runs on Atlassian badge. To know more about Runs on Atlassian, see this developer blog post.
Note, the removal of egress does not require a major version update of apps.
As announced early Sep https://community.developer.atlassian.com/t/we-are-making-app-management-easier-for-our-cloud-admins/83303 we are now in the final phase of moving the in-product app management experience (UPM) across to Connected Apps which can be accessed from admin.atlassin.com.
The app management entry point in products will remain and we will start to progressively direct admins to Connected Apps
Roll out start: 10th Feb 2025
Roll out end: 19th Feb 2025
All key UPM features will become available in Connected Apps before we deprecate the experience and further improvement will be added over time.
Only the UPM Frontend will be deprecated. This change does not affect UPM APIs. No action is required by developers.
We understand many of you are just getting back from the holidays and are also gearing up for Atlas Camp next week. Due to this, we will be pushing the hard block from Jan 31, 2025 to Feb 14, 2025 to provide you with some additional time, learn more here
For apps still in violation, we will work in close collaboration with you, and you will receive further communication outlining the subsequent steps to resolve the violation.
On Feb 15, 2024, we officially ended support for our server products. Customers were no longer able to purchase, renew, upgrade, or receive any further support for all Jira, Confluence, Bitbucket, Bamboo, and Crowd server apps.
In June 2025, we will be removing the Server listings from the Atlassian Marketplace. Post these changes for all apps (besides Fisheye and Crucible) -
Server-only app listings will be removed from the Marketplace.
Server pages for apps with server hosting type will be removed.
For more information and nuances, please check this QRG.
Following the deprecation announcements on October 24, 2024, and November 14, 2024, we have now removed the V1 Marketplace APIs.
Please switch to the applicable V2 alternatives listed in the More Details
section.
Method | Path | V2 API alternative | |
---|---|---|---|
1 | GET | /rest/1.0/applications/{applicationKey} | |
2 | GET | /rest/1.0/applications | |
3 | GET | /rest/1.0/applications/{applicationKey}/latest | |
4 | GET | /rest/1.0/applications/{applicationKey}/{applicationBuildNumber} | |
5 | GET | /rest/1.0/plugins/archive/{appKey} | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-archived-get |
6 | GET | /rest/1.0/categories | |
7 | GET | /rest/1.0/plugins/{appKey} | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
8 | GET | /rest/1.0/plugins/{appKey}/feedback | |
9 | GET | /rest/1.0/plugins/{appKey}/feedback/type | |
10 | GET | /rest/1.0/plugins/{appKey}/feedback/type/distribution | |
11 | GET | /rest/1.0/plugins/{appKey}/icon | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
12 | DELETE | /rest/1.0/plugins/{appKey}/icon | |
13 | GET | /rest/1.0/plugins/{appKey}/logo | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
14 | DELETE | /rest/1.0/plugins/{appKey}/logo | |
15 | GET | /rest/1.0/plugins/{appKey}/banner | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
16 | DELETE | /rest/1.0/plugins/{appKey}/banner | |
17 | GET | /rest/1.0/plugins/{appkey}/tokens/{token} | |
18 | DELETE | /rest/1.0/plugins/{appkey}/tokens/{token} | |
19 | GET | /rest/1.0/plugins/{appkey}/tokens | |
20 | POST | /rest/1.0/plugins/{appkey}/tokens | |
21 | GET | /rest/1.0/plugins/{appkey}/pricing | |
22 | GET | /rest/1.0/plugins/{appkey}/pricing/draft | |
23 | GET | /rest/1.0/plugins/vendor/{vendorId} | |
24 | GET | /rest/1.0/plugins | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-get |
25 | GET | /rest/1.0/plugins/{appKey}/version/{appVersion} | |
26 | GET | /rest/1.0/plugins/{appKey}/build-number/{buildNumber} | |
27 | PUT | /rest/1.0/plugins/{appKey}/build-number/{buildNumber} | |
28 | GET | /rest/1.0/plugins/{appKey}/version/{buildNumber}/screenshots/index | |
29 | DELETE | /rest/1.0/plugins/{appKey}/version/{buildNumber}/screenshots/index | |
30 | POST | /rest/1.0/uploads/artifact/ | |
31 | POST | /rest/1.0/uploads/artifact/fetch | |
32 | POST | /rest/1.0/uploads/image/{imageType} | |
33 | GET | /rest/1.0/vendors/{vendorId} | |
34 | DELETE | /rest/1.0/vendors/{vendorId}/contacts/{atlassianAccountId} | |
35 | DELETE | /rest/1.0/vendors/{vendorId}/{imageType} | |
36 | GET | /rest/1.0/plugins/{appkey}/similar | NA |
37 | GET | /rest/1.0/plugins/app/{applicationKey} | NA |
38 | GET | /rest/1.0/plugins/app/{applicationKey}/filterBy | NA |
39 | GET | /rest/1.0/plugins/filterBy | NA |
40 | GET | /rest/1.0/plugins/search | NA |
41 | GET | /rest/1.0/vendors | NA |
42 | GET | /rest/1.0/reference | NA |
43 | GET | /rest/1.0/reference/applicationStatuses | NA |
44 | GET | /rest/1.0/reference/applicationVersionStatuses | NA |
45 | GET | /rest/1.0/ | NA |
46 | GET | /rest/1.0/users/{atlassianAccountId} | NA |
We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com
We're updating how we provide packages for customers and partners to develop with our platforms. Starting February 1, 2025, we will discontinue providing third-party packages on packages.atlassian.com. Instead, customers and partners must fetch these packages directly from the original upstream repositories.
For details on how this change affects you and for guidance on migration, please refer to the documentation available on Atlassian Developer .
Dear Partners,
We are updating the look and feel of the "Create New Version" and "Make Version Public" flows in the partner portal for version publishing. These updates are aimed at simplifying the app version creation workflow. The functionality of the different components and the creation experience will remain the same; these updates are limited to visual changes only.
Initially, a small percentage of partners will gain access to these updates, with a phased rollout planned for all partners to complete by Feb 14, 2025. For more information, please refer to the Quick Reference Guide(QRG) here.
p.s Please note that the “Publish App” UI will not undergo any changes as part of this.
To help with discount information for zero-dollar transactions, we have now included the discount amount to provide context on the total discount amount for the given license. This information was also present earlier but only for a limited number of $0 transactions; it has now been populated for all $0 transactions that have discounts.
Data can be seen in the purchaseDetails.discounts
array field of the transaction API. Partners can fetch this data using the lastUpdated
field of this API. Change is live in production starting Jan 13, 2025(today).
We have back-filled the data for zero-dollar transactions for approximately 86,000 transactions across partners, and we will provide this discount information for future zero-dollar transactions. This includes all currently active and historical $0 transactions in the past that have a discount associated with them.
This is a reminder about the changelog announcements issued on October 24, 2024, and November 14, 2024, concerning the deprecation of legacy REST APIs.
The deprecation of Marketplace V1 REST APIs will take effect on January 10, 2025 (Friday). These APIs are intended for Atlassian usage and will not be supported after this date.
Please review your current implementations and make any necessary adjustments before January 10, 2025, to ensure continued functionality.
See the More details
section for the APIs list.
The following APIs will no longer be available from Jan 10, 2025 :
Method | Path | V2 API alternative | |
---|---|---|---|
1 | GET | /rest/1.0/applications/{applicationKey} | |
2 | GET | /rest/1.0/applications | |
3 | GET | /rest/1.0/applications/{applicationKey}/latest | |
4 | GET | /rest/1.0/applications/{applicationKey}/{applicationBuildNumber} | |
5 | GET | /rest/1.0/plugins/archive/{appKey} | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-archived-get |
6 | GET | /rest/1.0/categories | |
7 | GET | /rest/1.0/plugins/{appKey} | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
8 | GET | /rest/1.0/plugins/{appKey}/feedback | |
9 | GET | /rest/1.0/plugins/{appKey}/feedback/type | |
10 | GET | /rest/1.0/plugins/{appKey}/feedback/type/distribution | |
11 | GET | /rest/1.0/plugins/{appKey}/icon | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
12 | DELETE | /rest/1.0/plugins/{appKey}/icon | |
13 | GET | /rest/1.0/plugins/{appKey}/logo | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
14 | DELETE | /rest/1.0/plugins/{appKey}/logo | |
15 | GET | /rest/1.0/plugins/{appKey}/banner | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
16 | DELETE | /rest/1.0/plugins/{appKey}/banner | |
17 | GET | /rest/1.0/plugins/{appkey}/tokens/{token} | |
18 | DELETE | /rest/1.0/plugins/{appkey}/tokens/{token} | |
19 | GET | /rest/1.0/plugins/{appkey}/tokens | |
20 | POST | /rest/1.0/plugins/{appkey}/tokens | |
21 | GET | /rest/1.0/plugins/{appkey}/pricing | |
22 | GET | /rest/1.0/plugins/{appkey}/pricing/draft | |
23 | GET | /rest/1.0/plugins/vendor/{vendorId} | |
24 | GET | /rest/1.0/plugins | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-get |
25 | GET | /rest/1.0/plugins/{appKey}/version/{appVersion} | |
26 | GET | /rest/1.0/plugins/{appKey}/build-number/{buildNumber} | |
27 | PUT | /rest/1.0/plugins/{appKey}/build-number/{buildNumber} | |
28 | GET | /rest/1.0/plugins/{appKey}/version/{buildNumber}/screenshots/index | |
29 | DELETE | /rest/1.0/plugins/{appKey}/version/{buildNumber}/screenshots/index | |
30 | POST | /rest/1.0/uploads/artifact/ | |
31 | POST | /rest/1.0/uploads/artifact/fetch | |
32 | POST | /rest/1.0/uploads/image/{imageType} | |
33 | GET | /rest/1.0/vendors/{vendorId} | |
34 | DELETE | /rest/1.0/vendors/{vendorId}/contacts/{atlassianAccountId} | |
35 | DELETE | /rest/1.0/vendors/{vendorId}/{imageType} | |
36 | GET | /rest/1.0/plugins/{appkey}/similar | NA |
37 | GET | /rest/1.0/plugins/app/{applicationKey} | NA |
38 | GET | /rest/1.0/plugins/app/{applicationKey}/filterBy | NA |
39 | GET | /rest/1.0/plugins/filterBy | NA |
40 | GET | /rest/1.0/plugins/search | NA |
41 | GET | /rest/1.0/vendors | NA |
42 | GET | /rest/1.0/reference | NA |
43 | GET | /rest/1.0/reference/applicationStatuses | NA |
44 | GET | /rest/1.0/reference/applicationVersionStatuses | NA |
45 | GET | /rest/1.0/ | NA |
46 | GET | /rest/1.0/users/{atlassianAccountId} | NA |
UPDATE
We’ve recently added no-egress properties to the webtrigger
module, which is now in EAP. Using these new properties can help apps using webtriggers
to become eligible for the Runs on Atlassian program.
From Jan 6, 2025, the use of web triggers will exclude apps from the Runs on Atlassian eligibility criteria.
This is because Forge web triggers currently allow for the egress of customer data returned in response to third-party requests.
While we understand that using web triggers is unavoidable for some use cases involving external systems, we’re also looking to uphold the integrity of the Runs on Atlassian badge for customers.
Eligibility requirements may change leading up to the launch of the program.
Atlassian Marketplace APIs will now share data for lifetime free licenses data to our partners through the licenses report.
This license data for life time free apps is based on analytics data generated during the installations of these apps and has been transformed into free licenses. These licenses will only be available via the APIs and not through the user interface on the Marketplace portal.
Partners will be able to access this data via the existing license report APIs (GET as well as EXPORT) using the new showLifeTimeFreeLicenses
filter:
https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses?showLifeTimeFreeLicenses=true
- Get life time free apps licenses data
https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses/async/export?showLifeTimeFreeLicenses=true
- Initiate async export of life time free apps licenses data
https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses/export?showLifeTimeFreeLicenses=true
- Export life time free apps licenses data
More details section contains the applicable fields from licenses report for these new free licenses.
Partners can start accessing this data from Jan 6, 2025. We highly recommend all partners to take a look at the quick reference guide to understand more about this data.
Fields applicable for the new free licenses:
Field | Purpose |
---|---|
| A unique random identifier used to identify this installation/line item. Although the format of this field differs from the Note: This is not an actual entitlement Id generated by our billing system but a replacement for it since licenses are not actually created for these installations. For free apps that were once paid or compass free (lifetime) apps, actual entitlements are created in our billing system just like for paid apps. |
| A unique random identifier used to identify this installation/line item. Although the format of this field differs from the Note: This is not an actual entitlement number but a replacement for it since licenses are not actually created for these installations |
| The identifier for the parent product license, for example "123a1234-1234-1ab2-1234-1234a1234567". |
| The customer facing identifier for the parent product license, for example "E-123-456-789". |
| The unique identifier representing the cloud site that the app is installed in. |
| The hostname for the cloud site that the app is installed in. |
| The unique identifier for this app, for example "com.atlassian.confluence.plugins.test". |
| The display name of the app, for example "Test for Confluence". |
| The platform on which the app runs (either 'Server', 'Data Center' or 'Cloud'). This will always be cloud since we are only extending this for free cloud apps. |
| The date on which the data was last updated. This can be used to identify when historical license data is updated for any reason. |
| The type for the licenses. In this case, license type will always be ‘FREE’. |
| The date on which license maintenance begins. This will be the installation date for this data. |
| The unique identifier for the status of this license:
|
| The user/edition count, for example, 100 Users. |
| The name of the organisation which purchased the app. |
| The name of the country in which the customer was billed. |
| The name of the region in which the customer was billed. |
| Contact details of the technical admin for the license. |
| Contact details of the billing admin for the license. |
| The partner's organisation name. |
| The type of partner ('Expert', 'Reseller' or 'Corporate_reseller'). The type will be 'Unknown' if we are unable to determine it. |
| Contact details of the partner for billing. |
| The number of months for which evaluation license parent product is valid. |
| Name of the parent product on which the app is hosted, for example "Jira". |
| A short description of the pricing tier or user level of the license's parent product, for example, "Premium". |
| Whether the licence is installed on sandbox site or not. |
| The source of the license based on the customer domain. Values can be 'Atlassian' or 'Non-Atlassian' |
Confluence cloud apps on Atlassian Marketplace now offer up to 150k user tier pricing in line with Confluence cloud. The following new tiers are now available:
50,001-60,000
60,001-70,000
70,001-80,000
80,001-90,000
90,001-100,000
100,001-110,000
110,001-120,000
120,001-130,000
130,001-140,000
140,001-150,000
Action required: Pricing for the new tiers will default to the price for 45,001-50,000 users until Marketplace Partners adjust new per-user pricing for newly added tiers.
Please note that the customer experience changes will not take place until around the second week of January.
Owing to the upcoming holiday season and partner requests, we are providing a final extension for existing apps with unresolved naming violations, relaxing the hard block for Marketplace apps until January 31, 2025.
Partners with open tickets related to app name violations must address these issues by the new deadline. Failure to do so will render their app names non-compliant with Atlassian's brand guidelines. We have been sending reminders and will continue to provide updates and support to help you transition smoothly before the deadline.
Key Updates and Timelines:
Hard Block for Current Apps with Violations:
A hard block for existing app names with violations will take effect on January 31, 2025. All apps must be updated to comply with the guidelines before this date.
Soft Block for Existing Apps:
As of October 29, 2024, a soft block has been in place for existing apps with naming violations. Partners receive warnings during app version or name updates, but updates are not currently blocked.
Hard Block for New Apps:
Effective October 29, 2024, all new apps must comply with updated branding guidelines. Non-compliant app names will not be accepted for approval submissions.
We appreciate your cooperation as we work together to maintain a consistent and fair Marketplace.
We’re introducing a new program Runs on Atlassian as a Preview on Forge.
The program helps customers identify Forge apps that have no data egress and use data residency-enabled storage on the Atlassian Marketplace via a Runs on Atlassian
badge.
To know more about the Runs on Atlassian program, visit https://go.atlassian.com/runs-on-atlassian.
To check if your app is eligible for Runs on Atlassian, go to the Forge CLI documentation.
Eligibility requirements may change leading up to the launch of the program.
Rate this page: