Organization API failed due to new user management experience

Question

Hi,

I have issue while accessing

POST URL: https://api.atlassian.com/admin/v1/orgs/[my-org-id]/users/search

Request Body:

{ "emailDomains": { "contains": "mydomain.com" } }

Request Header:

* content-type: application/json
* accept: application/json
* authorization: Bearer [org-api-token]
* content-length: 58

response is 400 Bad Request with payload as following:

{ "errors": [ { "code": "ADMIN-400-4", "status": "400", "title": "INVALID_PARAM", "detail": "Organization: [my-org-id] is not with the new user management experience" } ] }

questions and additional info:

* What is the root cause for this issue? and how do I solve this issue?
* I'm an Org Admin recently

Thanks,

John

Richard White _TechTime_ · Accepted Answer

Hi John,

That particular user search API is only available if your organisation is using the "New user management experience" - see docs here: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v1-orgs-orgid-users-search-post

There is the get managed users endpoint - which works on old user management experience, but is much slower and can only select managed users.

The main reason not to switch to new user management experience is if you may need to merge organisations in the future where there are multiple sites (not possible in new experience) - https://support.atlassian.com/organization-administration/docs/should-i-merge-my-atlassian-organizations/

There are a number of other small UI and technical differences between the experiences.

If you don't want to change experiences - I highly recommend get in touch with Atlassian support. The more voices showing that these API's are required for organisations using the old experience, the better.

Kieren _SmolSoftware_ · Accepted Answer

In addition to what @Richard White _TechTime_ has said; the most likely reason you’re not on the new user management experience is you have multiple sites in your organization and you either have SCIM and/or use some group features in Jira that aren’t supported by group rename.

Richard makes a good point about the differences between the two experiences, and the lost org merge functionality in the new experience. From memory group renaming is also available on the new experience, not sure if it’s available on the old experience…

Either way, it’s best you reach out to Atlassian Support to discuss the details around why your specific org isn’t on the new experience and what it would take to get you onto the new experience.