Deprecation of Marketplace V2 APIs

Marketplace General Discussion
21

No, @FatimaAhmed , this endpoint is not included. You can check the specific APIs in the more details section.

22

Hi all, thank you for your feedback on the deprecation of rest/2/addons API. After hearing from our partners, we have decided to provide an alternative way for you to retrieve similar data. We are currently exploring a file based download mechanism and will share more soon.

Additionally, we will also be delaying the deprecation of this particular API until an alternative mechanism is available.

6 Likes
23

Hi Kelsey,

Additionally, we will also be delaying the deprecation of this particular API until an alternative mechanism is available.

Do you confirm that Atlassian Marketplace API v2 is not deprecated until further notice?
Will you provide a way to list addons, keywords, pricing and user counts?
Is the project of dropping the v2 still ongoing?

1 Like
24

This morning our customer experienced a problem with Atlassian’s Ansible playbook used to build a Jira/JSM DC installation, specifically where this API is used to identify what JSM version to use with the base Jira version

GET marketplace.atlassian.com/rest/2/products/key/{productKey}/versions/name/{versionName}

This playbook has been used daily, and since at least 10am NZST, 2 August 2025 the API started responding with HTTP 410 Gone. As reported by others on Marketplace slack for a different API – a call from a browser without authentication would still succeed for this one too.

4 Likes
25

@PriyaAggarwal @KelseyVanScoy

We have noticed the same issue. Many endpoints (not deprecated) no longer work when called outside of a browser. Error code: 410 - Gone.

This has broken our ETL flows, so we are waiting for a solution.

26

The Get Vendor API (GET https://marketplace.atlassian.com/rest/2/vendors/{vendorId}) has also started returning 410 Gone.

As best I can tell, this endpoint was not listed in any of the announcements
regarding deprecation of V2 endpoints?

27

I had an issue last week where the v2 transactions endpoint was returning 502 (not a 403) on an old but non-expired API key. Replaced the API key and it worked again. This was also outside a browser.

28

@PriyaAggarwal / @KelseyVanScoy (I’m specifically mentioning you both as the only Atlassian Staff previously present in this thread)

Are you able to comment on the above?

The Get Vendor API recently started returning 410 Gone responses, yet it is not in any of the deprecations lists above or in the Changelog, nor does it have the “DEPRECATED” label on it in the API docs.

I’m aware that Get Vendors (plural), which is the endpoint that previously could be used to get a list of all vendors, is deprecated. I’m specifically referring here to the endpoint that returns details for a single vendorId.

We need to understand whether we should start modifying our internal tooling that uses this endpoint, or whether it was simply an oversight that accidentally saw it included in the last round of deprecations.

Thanks,
Scott

29

@scottohara do a P1 severity ECOHELP ticket. I get fast responses reporting breaking changes through there.

30

@scottohara , the Get Vendor API change is related to this announcement - https://developer.atlassian.com/changelog/#CHANGE-1834

31

Thank you.

Can I suggest that you update the Marketplace REST V2 docs to mark these endpoints as deprecated?

That would have save us a lot of time.

2 Likes
32

That’s a valid ask @scottohara. We’re on it.
Thank you.

33

Hello @KelseyVanScoy

According to: Deprecation of Marketplace V2 APIs - #22 by KelseyVanScoy

You mention that there will be alternative API provided.

V2 API - stopped working and I do not see any alternative API.

Can you point me to alternative API?

Thanks

34

@KelseyVanScoy the /rest/2/addons API was deprecated once again today if I understand the announcement correctly.

Could you please point us to this alternative mechanism which should now be available? Thanks!

5 Likes
35

Also, I couldn’t find a replacement for /rest/2/addons/{addonKey}/pricing/{cloudOrServer}/{liveOrPending} - where would we get and update pricing for apps in V3?

The QRG says:

API contracts are being finalised. We will share the contracts in the next communication.

How can these API be deprecated if there is no replacement available? Or are they not yet deprecated?

3 Likes
36

Hi @BenRomberg apologies for the delayed response and @KrzysztofBogdan2 this page is the source of truth. Please direct any open questions there and one of the Marketplace Product Managers will get back to you.

37

With the obvious push to v3, can someone tell me if they figured out a simple way of downloading the most recent version of an app given the plugin key? I’ve been able to figure out how to cobble together using the plugin key on v3 to hit the rest/3/app-software/app-key/ endpoint to get the appSoftwareId. Then use that to get the app software information via the ret/3/app-software//versions. To do comparison of all versions with max/minbuildnumber. After all of that to get the buildNumber I care about and then what endpoint do I use to even get the app after identifying it? I can see no get in the documentation. Oh and the link posted by @KelseyVanScoy seems invalid because I can’t sign in and get to it.