This API is available only to customers using the new user management experience. Learn more about the new user management experience.
This tutorial will help you to:
Users with emails whose domain is claimed can still be found in Managed accounts under Directory even after being removed.
To complete this tutorial, you need the following:
API token ≠ API key:
AccountId is a required path parameter to remove user access.
An API token is needed to get the accountId in the next step. Use an API token to authenticate your script.
To create an API token:
To get the accountId:
Use the Jira User Search API with the API token and Basic authentication to get the accountId: GET /rest/api/3/users/search
1 2curl --request GET \ --url 'https://your-domain.atlassian.net/rest/api/3/users/search' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json'
Search the results by email address or name to find the correct accountId.
Learn more about the Jira API.
If you don’t have Jira, export a .csv of the user list. Learn how to export users from a site
The Remove user access script uses an API key as a Bearer access token. It also uses the Organization ID field as a path parameter.
To create an API key and get the Organization ID:
Learn more about the API keys.
Use the accountId, API key and Organization ID from the previous steps to remove user access: DELETE /admin/v1/orgs/{orgId}/directory/users/{accountId}
1 2curl --request DELETE \ --url 'https://api.atlassian.com/admin/v1/orgs/{orgId}/directory/users/{accountId}' \ --header 'Authorization: Bearer <access_token>'
Make your first request and get started with the Remove User Access API and get more information on error codes.
Rate this page: