About

The user provisioning API for Atlassian Cloud is a RESTful API that allows you to manage users and groups. With this API, you can write your own integration with your external identity provider (IdP) using the SCIM 2.0 protocol to programmatically manage your Atlassian Cloud users and groups for Jira Cloud and Confluence Cloud products. For example, you can provision and deprovision users and groups, update users' details such as the email address and manage their access to the Cloud products. For details on how user provisioning works, see User provisioning.

Getting Started with the user provisioning API

The user provisioning API follows the standards of the System for Cross-domain Identity Managaement (SCIM) specification. Before you start using the API, have a read of how the user provisioning functionality works in Atlassian Cloud at user provisioning.

Enabling the user provisioning API

The API key protects the user provisioning APIs. This key gives full administrative access to your organization's directory, allowing the API client to create and update users, groups and user attributes and change users' group membership. You should use the API key as a bearer token in the HTTP request Authorization header. To get the bearer token, follow the instructions at Authorization.

The following example demonstrates how to retrieve a list of users from a brand new directory with the API key.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
# Request
GET /scim/directory/2fb21891-7bee-4c2d-a61a-ade3834c8b2b/Users HTTP/1.1
Host: api.atlassian.com
Content-type: application/json
Authorization: Bearer <Access Token>

# Response
HTTP/2 200
content-type: application/scim+json
{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:ListResponse"
  ],
  "totalResults": 0,
  "startIndex": 1,
  "itemsPerPage": 10000,
  "Resources": []
}

Status codes

We follow the standard HTTP status code definition. See W3C Status Code Definitions for the detailed code definitions.

SCIM API limitations

  1. User
  • A user account only gets created when it has an email address with a domain you have verified.
  • Deleting a user account via the user provisioning API is not supported. The DELETE operation for a user deactivates the user account, which is the same as setting the active flag to false.
  • A total number of 5000 user limit is enforced per directory. This limit exists because some products have an upper bound for total supported users.
  1. Group
  • When you sync a group that has the same name as an existing group in the organization, the group sync will fail and you'll get an error.
  • If the API creates a group in the organization's directory that has the same name of a site's group (e.g. confluence-users), the API successfully creates the group in the directory but fails to propagate the group to the organization's sites. You'll see this event in the audit log.
  • Changing group names isn't supported. Renaming groups after they've synced to your Atlassian organization isn't supported in this release of User Provisioning API. This is because some parts of the products rely on group names and changing the group name would result in users not being able to interact with the products correctly. To rename a group, create a new group with the desired name, update membership, and then delete the old group.
  1. Authorization
  • You can only view and store the Access Token (API key) during directory creation. You will have to "Rotate" the token if you can't locate it.

Users

User attributes that can be updated through the user provisioning API

User profile fieldSCIM fieldAttribute typeRequired
Display namedisplayNameSingularfalse
Email addressemailsMulti-Valuedtrue
OrganizationorganizationSingularfalse
Job titletitleSingularfalse
TimezonetimezoneSingularfalse
DepartmentdepartmentSingularfalse
Preferred languagepreferredLanguageSingularfalse

Retrieve a user from a directory by userId

GET /scim/directory/{directoryId}/Users/{userId}

This operation retrieves a user from a directory by userId.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

userId Required

string

User Id

Query parameters
attributes

string

Resource attributes to be included in response, it should be used mutual exclusive with "excludedAttributes". Example: userName,emails.value etc

excludedAttributes

string

Resource attributes to be excluded in response, it should be used mutual exclusive with "attributes". Example: userName,emails.value etc

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Users/{userId}?attributes={attributes}' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

User has been returned successfully.

Content typeValue
application/json

Scim user

application/scim+json

Scim user

Update user information in a directory via user attributes

PUT /scim/directory/{directoryId}/Users/{userId}

This Operation updates a user's information in a directory by userId via user attributes. User information will be replaced attribute-by-attribute, with the exception of immutable and read-only attributes. Existing values of unspecified attributes will be cleaned.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

userId Required

string

User Id

Query parameters
attributes

string

Resource attributes to be included in the response. The value of this parameter should be mutually exclusive with that of the "excludedAttributes" parameter. Example: userName,emails.value

excludedAttributes

string

Resource attributes to be excluded in the response. The value of this parameter should be mutually exclusive with that of the "attributes" parameter. Example: userName,emails.value

Body parameters
Content typeValue
application/json

Scim user

application/scim+json

Scim user

Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
curl --request PUT \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Users/{userId}' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "userName": "<string>",
  "emails": [
    {
      "value": "<string>",
      "type": "<string>",
      "primary": true
    }
  ],
  "name": {
    "formatted": "<string>",
    "familyName": "<string>",
    "givenName": "<string>",
    "middleName": "<string>",
    "honorificPrefix": "<string>",
    "honorificSuffix": "<string>"
  },
  "displayName": "<string>",
  "nickName": "<string>",
  "title": "<string>",
  "preferredLanguage": "<string>",
  "department": "<string>",
  "organization": "<string>",
  "timezone": "<string>",
  "phoneNumbers": [
    {
      "value": "<string>",
      "type": "<string>",
      "primary": true
    }
  ],
  "active": true
}'

Responses

User has been updated successfully.

Content typeValue
application/json

Scim user

application/scim+json

Scim user

Set a user to deactivated and the user will not be available for future requests until being activated again.

DELETE /scim/directory/{directoryId}/Users/{userId}

This operation set a user to deactivated by userId and the user will not be available for future requests until being activated again. Any future operations for the deleted user will return the 404 (resource not found) error.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

userId Required

string

User Id

Example

1
2
3
curl --request DELETE \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Users/{userId}' \
  --header 'Authorization: Bearer <access_token>'

Responses

User has been deleted.

Update user information in a directory via the PATCH operation

PATCH /scim/directory/{directoryId}/Users/{userId}

This operation updates a user's information in a directory by userId via the PATCH operation. Refer to GET /ServiceProviderConfig for details on the supported operations.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

userId Required

string

User Id

Query parameters
attributes

string

Resource attributes to be included in the response. The value of this parameter should be mutually exclusive with that of the "excludedAttributes" parameter. Example: userName,emails.value etc.

excludedAttributes

string

Resource attributes to be included in the response. The value of this parameter should be mutually exclusive with that of the "attributes" parameter. Example: userName,emails.value etc.

Body parameters
Content typeValue
application/json

Request payload to patch.

application/scim+json

Request payload to patch.

Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
curl --request PATCH \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Users/{userId}' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "schemas": [
    "<string>"
  ],
  "operations": [
    {
      "op": "<string>",
      "path": "<string>",
      "value": {
        "array": true,
        "null": true,
        "valueNode": true,
        "containerNode": true,
        "missingNode": true,
        "object": true,
        "nodeType": "ARRAY",
        "pojo": true,
        "number": true,
        "integralNumber": true,
        "floatingPointNumber": true,
        "short": true,
        "int": true,
        "long": true,
        "double": true,
        "bigDecimal": true,
        "bigInteger": true,
        "textual": true,
        "boolean": true,
        "binary": true,
        "float": true
      }
    }
  ]
}'

Responses

User has been updated successfully.

Content typeValue
application/json

Scim user

application/scim+json

Scim user

Retrieve users from a directory

GET /scim/directory/{directoryId}/Users

This operation retrieves users from a directory. Filtering is supported with a single exact match (eq) against the userName and externalId attributes. Pagination is supported. Sorting is not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

Query parameters
attributes

string

Resource attributes to be included in response, it should be used mutual exclusive with "excludedAttributes". Example: userName,emails.value etc

excludedAttributes

string

Resource attributes to be excluded in response, it should be used mutual exclusive with "attributes". Example: userName,emails.value etc

filter

string

Filter for userName or externalId, example: userName eq "Atlassian"

startIndex

integer

A 1-based index of the first query result.

Default: 1, Format: int32
count

integer

Desired maximum number of query results in the list response page.

Format: int32

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Users' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

Users have been returned successfully.

Content typeValue
application/json

Scim user list response

application/scim+json

Scim user list response

Create a user in a directory

POST /scim/directory/{directoryId}/Users

This operation creates a user in a directory. Attempt to create an existing user will fail with the 409 (Conflict) error. A user account only gets created when it has an email address with a verified domain. If a managed Atlassian account already exists on the Atlassian platform for the email address, the user in your IdP will be automatically linked to the user in your Atlassian organization.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

Query parameters
attributes

string

Resource attributes to be included in response, it should be used mutual exclusive with "excludedAttributes". Example: userName,emails.value etc

excludedAttributes

string

Resource attributes to be excluded in response, it should be used mutual exclusive with "attributes". Example: userName,emails.value etc

Body parameters
Content typeValue
application/json

Scim user

application/scim+json

Scim user

Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
curl --request POST \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Users' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "userName": "<string>",
  "emails": [
    {
      "value": "<string>",
      "type": "<string>",
      "primary": true
    }
  ],
  "name": {
    "formatted": "<string>",
    "familyName": "<string>",
    "givenName": "<string>",
    "middleName": "<string>",
    "honorificPrefix": "<string>",
    "honorificSuffix": "<string>"
  },
  "displayName": "<string>",
  "nickName": "<string>",
  "title": "<string>",
  "preferredLanguage": "<string>",
  "department": "<string>",
  "organization": "<string>",
  "timezone": "<string>",
  "phoneNumbers": [
    {
      "value": "<string>",
      "type": "<string>",
      "primary": true
    }
  ],
  "active": true
}'

Responses

User has been created successfully.

Content typeValue
application/json

Scim user

application/scim+json

Scim user

Groups

Retrieve a group from a directory by group Id

GET /scim/directory/{directoryId}/Groups/{id}

This operation retrieves a group from a directory by group Id.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

id Required

string

Group Id

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Groups/{id}' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

Group has been returned successfully.

Content typeValue
application/json

Scim group

application/scim+json

Scim group

Updates a group from a directory by groupId

PUT /scim/directory/{directoryId}/Groups/{id}

This operation updates a group from a directory by groupId.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

id Required

string

Group Id

Body parameters
Content typeValue
application/json

Scim group

application/scim+json

Scim group

Example

1
2
3
4
5
6
7
8
curl --request PUT \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Groups/{id}' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "displayName": "<string>"
}'

Responses

Group has been updated successfully.

Content typeValue
application/json

Scim group

application/scim+json

Scim group

Deletes a group in a directory

DELETE /scim/directory/{directoryId}/Groups/{id}

This operation deletes a group in a directory. Attempt to delete a non-existing group will fail with the 404 (Resource Not found) error.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

id Required

string

Group Id

Example

1
2
3
curl --request DELETE \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Groups/{id}' \
  --header 'Authorization: Bearer <access_token>'

Responses

Group has been deleted successfully.

Update group information in a directory via the PATCH operation

PATCH /scim/directory/{directoryId}/Groups/{id}

This operation updates a groups's information in a directory by groupId via the PATCH operation. You can use this API to manage group membership, i.e. adding users to or removing users from a group.

Changing group names isn't supported. Renaming groups after they've synced to your Atlassian organization isn't supported in this release of User Provisioning API. To rename a group, create a new group with the desired name, update membership, and then delete the old group.

In the following example of adding members to a group with the API, we omitted some HTTP headers and formatted JSON payloads for readability.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
# Request
PATCH /scim/directory/2fb21891-7bee-4c2d-a61a-ade3834c8b2b/Groups/50202593-bc47-45df-8fa0-3f63343aa3c1 HTTP/1.1
Accept: application/scim+json
Accept-Charset: utf-8
Content-Type: application/scim+json; charset=utf-8
Authorization: Bearer 0j6lDgrjU7HmGagocgLe
Host: api.atlassian.com

{
   "schemas":[
      "urn:ietf:params:scim:api:messages:2.0:PatchOp"
   ],
   "Operations":[
      {
         "op":"add",
         "path":"members",
         "value":[
            {
               "value":"c6993c94-dbda-40f1-b6f0-18c855522ade",
               "display":"dave.meyer@demotime.authteam.com"
            },
            {
               "value":"f0ae48f7-1466-445e-85ea-e83ef754aefd",
               "display":"lingbo.lu@demotime.authteam.com"
            },
            {
               "value":"432d6f10-2e28-454e-be99-0f8c732a046f",
               "display":"joanna@demotime.authteam.com"
            }
         ]
      }
   ]
}

# Response
HTTP/1.1 200
Content-Type: application/scim+json

{
   "schemas":[
      "urn:ietf:params:scim:schemas:core:2.0:Group"
   ],
   "id":"50202593-bc47-45df-8fa0-3f63343aa3c1",
   "displayName":"demotime-confluence-users",
   "members":[
      {
         "type":"User",
         "value":"f0ae48f7-1466-445e-85ea-e83ef754aefd",
         "display":"lingbo.lu@demotime.authteam.com",
         "$ref":"https://api.atlassian.com/scim/directory/2fb21891-7bee-4c2d-a61a-ade3834c8b2b/Users/f0ae48f7-1466-445e-85ea-e83ef754aefd"
      },
      {
         "type":"User",
         "value":"c6993c94-dbda-40f1-b6f0-18c855522ade",
         "display":"dave.meyer@demotime.authteam.com",
         "$ref":"https://api.atlassian.com/scim/directory/2fb21891-7bee-4c2d-a61a-ade3834c8b2b/Users/c6993c94-dbda-40f1-b6f0-18c855522ade"
      },
      {
         "type":"User",
         "value":"432d6f10-2e28-454e-be99-0f8c732a046f",
         "display":"joanna@demotime.authteam.com",
         "$ref":"https://api.atlassian.com/scim/directory/2fb21891-7bee-4c2d-a61a-ade3834c8b2b/Users/432d6f10-2e28-454e-be99-0f8c732a046f"
      }
   ],
   "meta":{
      "resourceType":"Group",
      "location":"https://api.atlassian.com/scim/directory/2fb21891-7bee-4c2d-a61a-ade3834c8b2b/Groups/50202593-bc47-45df-8fa0-3f63343aa3c1",
      "lastModified":"2018-09-26T17:49:09.420654Z",
      "created":"2018-09-26T17:41:35.49073Z"
   }
}
OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

id Required

string

Group Id

Body parameters
Content typeValue
application/json

Request payload to patch.

application/scim+json

Request payload to patch.

Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
curl --request PATCH \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Groups/{id}' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "schemas": [
    "<string>"
  ],
  "operations": [
    {
      "op": "<string>",
      "path": "<string>",
      "value": {
        "array": true,
        "null": true,
        "valueNode": true,
        "containerNode": true,
        "missingNode": true,
        "object": true,
        "nodeType": "ARRAY",
        "pojo": true,
        "number": true,
        "integralNumber": true,
        "floatingPointNumber": true,
        "short": true,
        "int": true,
        "long": true,
        "double": true,
        "bigDecimal": true,
        "bigInteger": true,
        "textual": true,
        "boolean": true,
        "binary": true,
        "float": true
      }
    }
  ]
}'

Responses

Group has been updated successfully.

Content typeValue
application/json

Scim group

application/scim+json

Scim group

Retrieve groups from a directory

GET /scim/directory/{directoryId}/Groups

This operation retrieves groups from a directory. Filtering is supported with a single exact match (eq) against the displayName attribute. Pagination is supported. Sorting is not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Directory Id

Query parameters
filter

string

Filter for displayName, example: displayName eq "SCIM_GROUP"

startIndex

integer

A 1-based index of the first query result.

Default: 1, Format: int32
count

integer

Desired maximum number of query results in the list response page.

Format: int32

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Groups' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

Groups have been returned successfully.

Content typeValue
application/json

Scim group list response

application/scim+json

Scim group list response

Create a group in a directory

POST /scim/directory/{directoryId}/Groups

This operation creates a group in a directory. Attempt to create a group with an existing name will fail with the 409 (Conflict) error.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Body parameters
Content typeValue
application/json

Scim group

application/scim+json

Scim group

Example

1
2
3
4
5
6
7
8
curl --request POST \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Groups' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "displayName": "<string>"
}'

Responses

Group has been created successfully.

Content typeValue
application/json

Scim group

application/scim+json

Scim group

Schemas

Retrieve all schemas

GET /scim/directory/{directoryId}/Schemas

Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Schemas' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string

Retrieve User Schemas

GET /scim/directory/{directoryId}/Schemas/urn:ietf:params:scim:schemas:core:2.0:User

Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Schemas/urn:ietf:params:scim:schemas:core:2.0:User' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string

Retrieve Group Schemas

GET /scim/directory/{directoryId}/Schemas/urn:ietf:params:scim:schemas:core:2.0:Group

Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Schemas/urn:ietf:params:scim:schemas:core:2.0:Group' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string

Retrieve User Enterprise Extension Schemas

GET /scim/directory/{directoryId}/Schemas/urn:ietf:params:scim:schemas:extension:enterprise:2.0:User

Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/Schemas/urn:ietf:params:scim:schemas:extension:enterprise:2.0:User' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string

Retrieve metadata about the supported SCIM features

GET /scim/directory/{directoryId}/ServiceProviderConfig

This is a service provider configuration endpoint providing supported SCIM features. Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/ServiceProviderConfig' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string

Service Provider Configuration

Retrieve types of resources available on a SCIM service provider (e.g., Users and Groups)

GET /scim/directory/{directoryId}/ResourceTypes

This is used to get all resources of the SCIM provider. Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/ResourceTypes' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string

Retrieve user resource type of this SCIM service provider

GET /scim/directory/{directoryId}/ResourceTypes/User

Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/ResourceTypes/User' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string

Retrieve group resource type of this SCIM service provider

GET /scim/directory/{directoryId}/ResourceTypes/Group

Filtering, pagination and sorting are not supported.

OAuth scopes required
None

Request

Path parameters
directoryId Required

string

Example

1
2
3
4
curl --request GET \
  --url 'https://api.atlassian.com/scim/directory/{directoryId}/ResourceTypes/Group' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Accept: application/json'

Responses

SCIM features metadata has been returned successfully.

Content typeValue
application/json

string

application/scim+json

string