Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Atlassian Access API

Our company is in the early access for Atlassian Access (see link). Does there exist an API that you all have exposed or are willing to expose to us which can automate functions of the Atlassian Access software? For instance, is there a call for deactivating a user in Atlassian Access?


Thank you.

4 answers

1 accepted

3 votes
Answer accepted
Rodrigo B_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 01, 2018

Hello @Adibou,

The current public APIs for users are only related to the products themselves and not our Identity Platform (Where the Atlassian accounts are) to perform actions such as Disable the entire Atlassian account or edit user details.

This set of APIs demand for an extra security layer, so we are developing public SCIM APIs that can match that requirement, check more about what this is on this documentation:

The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model, as well as binding documents to provide patterns for exchanging this schema using standard protocols. In essence: make it fast, cheap, and easy to move users in to, out of, and around the cloud.

You can track our progress on this feature by watching the following request:

There is no ETA right now but this is actively being worked as it is an important complement to user management on the Cloud and the Atlassian Access product.

Thank you & best regards,

Rodrigo Becker
Atlassian Cloud Support

2 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 01, 2018 • edited

We do indeed have a public facing documentation where all our public APIs can found :


There isn't an endpoint for deactivating users but there is one available for removing them which is still in its experimental phase:

Remove user  EXPERIMENTAL DELETE /rest/api/2/user

Removes user.




the username


user key

  • STATUS 400 Returned if the request is invalid or some other server error occurred.
  • STATUS 401 Returned if the user is not authenticated.
  • STATUS 204 Returned if the user was deleted successfully.
  • STATUS 403 Returned if the caller does not have permission to remove the user.
  • STATUS 404 Returned if the caller does have permission to remove user but the user does not exist.
1 vote
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 01, 2018

Hi Michael,

please be aware that the JIRA Cloud REST API is regarding the Cloud Instance user's accounts and it will not affect their Atlassian Accounts (managed Atlassian accounts with Atlassian Access, and also the user's unmanaged Atlassian Accounts, see [Atlassian Accounts for users|] for more details on Atlassian Accounts). 

For example, the delete request to the API will delete the user from the Cloud Instance (i.e from, so the user won't be able to log in this cloud instance until it's reinvited) but it will not affect its Atlassian Account (the user's Atlassian Account will still be active in for a managed Atlassian accounts or in for an unmanaged Atlassian account).


This is exactly the problem we are trying to solve. When we deactivate someone in Hipchat, Jira, and Bitbucket, we want them to show as inactive in since they are technically unable to access any of our accounts. Are you saying that this cannot currently be done?

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 02, 2018

Hey , indeed, as rodrigo mentioned, the atlassian account management is not available through API yet, there is the feature request for this.

Still, it appears to be already an important  work in progress in order to have this API implemented soon and applicable to atlassian access.

We use automation with Workato and need to be able to add/disable/delete Atlassian ID accounts via API.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events