There was a surprising announcement today about Marketplace V2 REST APIs being deprecated in May 2025. These include some important APIs that we’re currently using and I’m wondering why they are “intended for use through the Atlassian applications only”. Specifically, we’re using:
products should probably be replaced by addons, in which case we’re also actively using the following API that should, in our opinion, not be deprecated:
In any case, this deprecation was not announced in advance and there was no RFC that I’m aware of. There are probably a lot of other partners affected who have automated some parts of running their Marketplace business and I’m asking the team to reconsider some of the announced deprecations. Otherwise, we’ll have to find other ways of obtaining the necessary data, which not only makes our lives more difficult, but probably also increases the load on the Atlassian Marketplace.
Second this, the get calls on the version endpoints are heavily used by us in our build pipelines, and we mentioned as much in the survey that has been shared recently.
Yea, we are affected.
for https://ampin.app we are using /rest/2/addons and /rest/2/addons/{appKey}/versions
We can always move to crawling marketplace but that would suck.
I am not sure about logic behind this deprecation.
Not even from https://ampin.app/ perspective but
especially for those managing versions/releases via API.
We’re sorry for the typo in the announcement regarding the products resource APIs group. Thanks for bringing it to our notice timely. We have corrected the announcement now.
@PriyaAggarwal thanks, so at least the versions APIs for apps/addons are not affected.
However, the concern remains that the /rest/2/addons API will be deprecated.
Why is that necessary? Is it too much traffic from partners? Why was it noticed that these APIs were “intended for use through the Atlassian applications only” after being publicly documented for 5+ years? That doesn’t sound like a plausible reason to me.
I’d like to emphasize what Ben said and quote from the deprecation notice:
We’re also announcing here the deprecation of V2 APIs that are intended for use through the Atlassian applications only.
This is a completely counter factual representation of the Marketplace REST API’s history. To the contrary, we have always been encouraged to build our own automation and reporting solutions atop the entire Marketplace REST API, as evidenced by literally the first sentence in the referenced V2 APIs:
The Marketplace API is a RESTful API that allows you to manage apps and your vendor account.
[…]
Version 2 is the latest release of the Marketplace API. Scroll down to view the latest API documentation for this version.
You cannot just take away these capabilities that are extensively used across the ecosystem without a proper discussion, deprecation period, and ideally sufficient replacements.
We all understand that APIs need to evolve and capabilities can be changed or even dropped for a myriad of reasons, but sabotaging your entire partner community like this ain’t the way.
As is, this v2 API deprecation is going to have a massive impact on many partners, who would rather spend the time on adding value for our mutual customers, and all this for no apparent (or at least not disclosed) good reason.
PS: The AWS success story is famously based on an ‘API first’ mandate. The Atlassian Marketplace has been one of the few areas where Atlassian actually tried to heed that approach, so it’s quite the irony, and frankly embarrassing, that you are removing public consumption of these readily available APIs that need to stay around for your internal use anyway, thereby forcing everyone to work around things via scraping again, like in ancient times …
To add to Steffen’s point, when the REST API V2 was released in 2016, the announcement was specifically directed at partners, suggesting that we could build it into our “business process and tooling”. The first paragraph of the announcement included a link describing how the API was “fully documented”, pointing to the entire API documentation, not some subset that is retroactively being declared as intended for internal use only.
It also describes the API as “supported”.
Here is the original announcement:
Could Atlassian consider taking a step back and publish this as a RFC, so the community can make a case for how these changes will impact their businesses?
Yeah this has all the stereotypical markings of newbie Atlassian staffers coming in, somehow getting the false impression that Marketplace APIs are only for internal use, and then being granted the responsibility to deprecate them.
I’ll agree on all comments above. Removing these APIs has a large impact on every partner (not only app vendors).
Looking at the Marketplace UI, it’s understandable, that the focus is customer centric but for the people who maintain data center environments, doing Cloud migration readiness assessments, setup migration environments, etc. it becomes already a pain as more and more server / data center related details (speaking about versions) are hided and requires an endless amount of clicks.
In the recent month i discovered that the UI doesn’t show up certain listings anymore where i needed certain plugin version details for an assessment, etc. I had to consult the API which still has the data that i needed and also gave me the artefacts that i needed.
So, never forget that the Marketplace has 2 audiences (customers / partners) that have different needs!
We also are relying on these API’s and would be quite badly affected if they are removed. We rely on them for the automation of our product deployments to marketplace. For us, it would be very time consuming to do these manually across all of our apps.
Did Atlassian do any analysis of the usage of these API’s before summarily deprecating them?
Thank you for your feedback and the post. Let me take a step back and clarify a few points, which I hope you would find useful. Firstly, since our current Marketplace system is nearly 13 years old, it has become increasingly challenging to develop and maintain for our Partners and Customers, we are transitioning towards a new microservices architecture as part of the Marketplace Technical Foundations Initiative. As part of this initiative, we are also reviewing APIs that we believe do not have significant partner usage and are for Atlassian Internal uses, primarily. We basically have categorised the deprecated V2 APIs that we announced in this deprecation notice Atlassian developer changelog in 3 buckets:
Internal Atlassian usage (22 out of 33 APIs listed below) - These APIs are specific to our UI application’s needs. To accelerate providing enhancements in the UI for our customers, we would need to change things and evolve APIs quickly. By mistake, they were listed on DAC in the past, but technically they are meant for Atlassian’s internal consumption only.
low usage (9 out of 33 APIs listed below) - Data indicates a disproportionately high usage via the User Interface compared to the APIs for these actions. There are relevant touchpoints in the UI that we believe are more suitable for these actions than the APIs.
Intentional deprecation (1 out of 33 APIs listed below) - GET marketplace.atlassian.com/rest/2/addons This API was initially created to support the Marketplace search experience, which has since transitioned to internal APIs. We understand that partners also use this API for purposes such as competitive analysis. However, it is not our intention to maintain this API moving forward. During the deprecation process, we assessed its impact and determined that it is not business-critical. As a result, we are not planning an immediate replacement. Our current focus is on prioritizing other architectural updates to the marketplace platform that we consider more critical at this time.
The table below outlines all the V2 APIs that have been deprecated without replacement and will be removed in May 2025, along with their respective categories. We genuinely invite your feedback to understand if any of these APIs align with your actual use cases. Your insights are invaluable as they will help us consider potential replacements that could better serve your needs.
I’m sorry for being blunt here, but this is contradicting, or at the very least confusing. Which business does not deem competitive analysis as business critical?
To how many Marketplace partners did you talk to before reaching the conclusion that this API is not business critical?
Please provide an alternative before deprecating the addons path. Otherwise, many partners will have to start crawling the Marketplace one way or another, which probably won’t help the stability of the Marketplace and create a lot of frustration and effort for Marketplace partners.
As an alternative, it might be sufficient for you to deprecate the text query parameter of the addons API since you mentioned the problematic support of the Marketplace search experience. I believe most of us partners could probably do without a few of the query parameters offered, as long as we can continue fetching the list of apps programmatically.
If you uphold a mistake for 12+ years, you basically can’t just say “oops sorry” anymore. As soon as you publish an API and document it, people will start using it. If you are going to deprecate it after 12 years, you better provide an alternative.
Just for context, apart from the competitive analysis there are also other tools that are using these endpoints, like builtwithconnect.com, forge.report and forge-apps.com
These tools have been used by Atlassian staff and customers and provide a valuable resource additional to the Atlassian Marketplace as they serve a different purpose.
By limiting Atlassian Marketplace partner use of the APIs, you are effectively limiting partner initiatives to provide services to customers (and Atlassian staff!) that Atlassian is never going to provide.
Modernising the Atlassian Marketplace tech stack is absolutely important, but modernisation is not a reason to deprecate endpoints without replacement. Removing Marketplace Partners access to valuable information is a business decision, not an engineering decision, and Atlassian is not being open about the reasoning behind that business decision, f*cking customers and partners along the way.
Despite ongoing feedback from the community, Atlassian seems to fall into the same loop of making decisions without a thorough impact assessment. When evaluating the impact on an ecosystem as large as Atlassian’s, it would be good practice to consult with partners before assessing whether a potential decision is not business-critical.
We have seen this quite often over the past year, and I could cite several examples—from the poor handling of the deprecation of Confluence APIs to the removal of extension points used by apps with tens of thousands of installations. Atlassian is making life for its partners increasingly complicated rather than simplifying it.
From my perspective, offering an API to access marketplace data is far more practical rather than constantly subjecting the platform to crawling or scraping operations. With an API, I can maintain control and provide an optimized service without burdening marketplace traffic. At most, you could restrict API access to limit traffic and ensure that only official Atlassian partners can access the data.
Let’s be realistic: do you really think that removing the API will discourage those who have invested significant resources in building business analytics for their operations? They will find “alternative” ways to obtain the same data.