# SCIM용 REST API 엔드포인트 REST API를 사용하여 SCIM으로 사용자 만들기 및 팀 멤버십을 자동화합니다. ## SCIM 정보 > \[!NOTE] > 이러한 엔드포인트는 personal access token (classic)을(를) 사용하는 인증만 지원합니다. 자세한 내용은 [개인용 액세스 토큰 관리](/ko/enterprise-server@3.22/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic)을(를) 참조하세요. GitHub 는 SCIM 지원 ID 공급자(ID 공급자)에서 사용할 엔드포인트를 제공합니다. IdP의 통합은 REST API를 사용하여 인증에 SAML SSO(Single Sign-On)를 사용하는 인스턴스에서 GitHub Enterprise Server 사용자 계정을 자동으로 프로비전, 관리 또는 프로비저닝 해제할 수 있습니다. [GitHub Enterprise Server에서 SCIM을 사용하여 사용자 프로비저닝 정보](/ko/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes)을(를) 참조하세요. 이러한 엔드포인트는 SCIM 2.0을 기반으로 합니다. 자세한 내용은 IdP의 설명서를 참조하거나 [IETF 웹 사이트의 사양](https://datatracker.ietf.org/doc/html/rfc7644)을 참조하세요. ### 루트 URL (기본 URL) IdP는 다음 루트 URL을 사용하여 인스턴스에 대해 GitHub Enterprise Server 이 범주의 엔드포인트와 통신할 수 있습니다. ```http http(s)://HOSTNAME/api/v3/scim/v2/ ``` 아래 엔드포인트 문서에 제공된 URL의 \*\*\*\* 부분을 포함하지 `enterprises/{enterprise}/`. 경로의 이 부분은 적용할 수 없습니다 GitHub Enterprise Server. 향후 이 문서에는 GitHub Enterprise Server에 대한 올바른 URL이 표시됩니다. 이 범주의 엔드포인트는 대/소문자를 구분합니다. 예를 들어 `Users` 엔드포인트의 첫 번째 문자는 대문자로 시작해야 합니다. ```shell GET /scim/v2/Users/{scim_user_id} ``` ### 인증 IdP의 SCIM 통합은 인스턴스에 대한 엔터프라이즈 소유자 GitHub Enterprise Server 를 대신하여 작업을 수행합니다. 자세한 내용은 [엔터프라이즈에서 역할의 기능](/ko/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles#enterprise-owners)을(를) 참조하세요. API 요청을 인증하려면 IdP에서 SCIM을 구성하는 사람은 personal access token (classic)`scim:enterprise`를 사용해야 하며, IdP는 이를 요청의 `Authorization` 헤더에 제공해야 합니다. personal access tokens (classic)에 대한 자세한 내용은 [개인용 액세스 토큰 관리](/ko/enterprise-server@3.22/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)을(를) 참조하세요. > \[!NOTE] > 엔터프라이즈 소유자는 이 범주의 엔드포인트에 대한 요청 인증을 생성하고 사용해야 personal access token (classic) 합니다. > Fine-grained personal access token 및 GitHub 앱 호출자는 현재 지원되지 않습니다. ### SAML 및 SCIM 데이터 매핑 GitHub Enterprise Server 사용자가 SAML SSO GitHub 를 사용하여 성공적으로 인증한 후 사용자를 SCIM 프로비전 ID에 연결합니다. ID를 성공적으로 연결하려면 SAML ID 공급자와 SCIM 통합에서 일치하는 고유 식별자를 사용해야 합니다. 사용자의 SAML 데이터와 SCIM 데이터가 일치하지 않는 경우 GitHub SAML 및 SCIM의 특성이 일치하지 않는 오류를 반환합니다. 이 오류에 대한 자세한 내용은 [엔터프라이즈의 ID 및 액세스 관리 문제 해결](/ko/enterprise-server@3.22/admin/managing-iam/understanding-iam-for-enterprises/troubleshooting-identity-and-access-management-for-your-enterprise#saml-and-scim-data-mismatch-errors)을(를) 참조하세요. GitHub에서 사용자를 SCIM으로 프로비저닝된 ID와 성공적으로 일치시키려면 다음 SAML 클레임 및 SCIM 특성이 필요합니다. ID 공급자는 사용자를 고유하게 식별하는 데 사용되는 필드와 다를 수 있습니다. #### SAML에 대한 Microsoft Entra ID SAML에 Entra ID(이전에는 Azure AD라고 함)를 사용하려면 다음 SAML 클레임 및 SCIM 특성이 일치해야 합니다. | SAML 클레임 | 일치하는 SCIM 특성 | | :-------------------------------------------------------------- | :----------- | | `http://schemas.microsoft.com/identity/claims/objectidentifier` | `externalId` | #### SAML용 기타 IdP들 SAML에 다른 IdP를 사용하려면, GitHub에서는 SAML "사용자 특성"에 구성된 "Username" 특성을 사용하여 아래 나열된 SCIM 특성과 일치시킵니다. 이 값을 비워두면, SAML "User attributes"의 "Username" 특성 값은 기본적으로 SAML `NameID`로 설정됩니다. SAML 구성에 대한 자세한 내용은 [엔터프라이즈에 대한 SAML Single Sign-On 구성](/ko/enterprise-server@3.22/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#configuring-saml-sso)을(를) 참조하세요. | SAML 클레임 | 일치하는 SCIM 특성 | | :------------------------------------------------------ | :----------- | | SAML "사용자 속성"에 구성된 "사용자 이름" 속성, 값이 비워진 경우에는 `NameID` 사용 | `userName` | ### 지원되는 SCIM 사용자 특성 이 범주의 `User` 엔드포인트는 요청의 매개 변수 내에서 다음 특성을 지원합니다. | 이름 | 유형 | 설명 | | :---------------- | :------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `displayName` | 문자열 | 사람이 이해할 수 있는 사용자 이름. | | `name.formatted` | 문자열 | 표시할 형식이 지정된 모든 중간 이름, 제목 및 접미사를 포함한 사용자의 전체 이름입니다. | | `name.givenName` | 문자열 | 사용자의 이름입니다. | | `name.familyName` | 문자열 | 사용자의 성입니다. | | `userName` | 문자열 | IdP에서 생성한 사용자의 사용자 이름입니다. 사용되기 전에 [정규화](/ko/enterprise-server@3.22/admin/managing-iam/iam-configuration-reference/username-considerations-for-external-authentication#about-username-normalization)를 거칩니다. | | `emails` | 배열 | 사용자 메일 목록입니다. | | `roles` | 배열 | 사용자 역할 목록입니다. | | `externalId` | 문자열 | 이 식별자는 IdP 공급자에 의해 생성됩니다. IdP에서 또는 `externalId` 엔드포인트를 사용하고 인스턴스의 사용자 이름 또는 전자 메일 주소와 같은 다른 알려진 특성을 필터링하여 사용자에 대한 [](#list-scim-provisioned-identities-for-an-enterprise) 정보를 찾을 GitHub Enterprise Server 수 있습니다. | | `id` | 문자열 | 인스턴스 SCIM 엔드포인트에서 생성된 식별자입니다. | | `active` | Boolean | ID가 활성 상태(`true`)인지 일시 중단(`false`)해야 하는지를 나타냅니다. | > \[!NOTE] > Most endpoints use `Authorization: Bearer ` and `Accept: application/vnd.github+json` headers, plus `X-GitHub-Api-Version: 2026-03-10`. Curl examples below omit these standard headers for brevity. ## List provisioned SCIM groups for an enterprise ``` GET /scim/v2/enterprises/{enterprise}/Groups ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Lists provisioned SCIM groups in an enterprise. You can improve query search time by using the excludedAttributes query parameter with a value of members to exclude members from the response. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`filter`** (string) If specified, only results that match the specified filter will be returned. Multiple filters are not supported. Possible filters are externalId, id, and displayName. For example, ?filter=externalId eq "9138790-10932-109120392-12321". * **`excludedAttributes`** (string) Excludes the specified attribute from being returned in the results. Using this parameter can speed up response time. * **`startIndex`** (integer) Used for pagination: the starting index of the first result to return when paginating through values. Default: `1` * **`count`** (integer) Used for pagination: the number of results to return per page. Default: `30` * **`enterprise`** (string) (required) The slug version of the enterprise name. ### HTTP response status codes * **200** - Success, either groups were found or not found * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **429** - Too many requests * **500** - Internal server error ### Code examples #### Example **Request:** ```curl curl -L \ -X GET \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups ``` **Response schema (Status: 200):** * `schemas`: required, array of string, enum: `urn:ietf:params:scim:api:messages:2.0:ListResponse` * `totalResults`: required, integer * `Resources`: required, array of object * `startIndex`: required, integer * `itemsPerPage`: required, integer ## Provision a SCIM enterprise group ``` POST /scim/v2/enterprises/{enterprise}/Groups ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Creates a SCIM group for an enterprise. If members are included as part of the group provisioning payload, they will be created as external group members. It is up to a provider to store a mapping between the externalId and id of each user. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`enterprise`** (string) (required) The slug version of the enterprise name. #### Body parameters * **`schemas`** (array of strings) (required) The URIs that are used to indicate the namespaces of the SCIM schemas. Supported values are: urn:ietf:params:scim:schemas:core:2.0:Group * **`externalId`** (string) (required) A unique identifier for the resource as defined by the provisioning client. * **`displayName`** (string) (required) A human-readable name for a security group. * **`members`** (array of objects) The group members. * **`value`** (string) (required) The local unique identifier for the member * **`displayName`** (string) (required) The display name associated with the member ### HTTP response status codes * **201** - Group has been created * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **409** - Duplicate record detected * **429** - Too many requests * **500** - Internal server error ### Code examples #### Example **Request:** ```curl curl -L \ -X POST \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups \ -d '{ "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:Group" ], "externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159", "displayName": "Engineering", "members": [ { "value": "879db59-3bdf-4490-ad68-ab880a2694745", "displayName": "User 1" }, { "value": "0db508eb-91e2-46e4-809c-30dcbda0c685", "displayName": "User 2" } ] }' ``` **Response schema (Status: 201):** * all of: * **object** * `schemas`: required, array of string, enum: `urn:ietf:params:scim:schemas:core:2.0:Group`, `urn:ietf:params:scim:api:messages:2.0:ListResponse` * `externalId`: string or null * `displayName`: string or null * `members`: array of objects: * `value`: required, string * `$ref`: required, string * `display`: string * **object** * `id`: string * `members`: array of objects: * `value`: string * `$ref`: string * `display`: string * `meta`: object: * `resourceType`: required, string, enum: `User`, `Group` * `created`: string * `lastModified`: string * `location`: string ## Get SCIM provisioning information for an enterprise group ``` GET /scim/v2/enterprises/{enterprise}/Groups/{scim_group_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Gets information about a SCIM group. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_group_id`** (string) (required) A unique identifier of the SCIM group. * **`excludedAttributes`** (string) Excludes the specified attribute from being returned in the results. Using this parameter can speed up response time. * **`enterprise`** (string) (required) The slug version of the enterprise name. ### HTTP response status codes * **200** - Success, a group was found * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **429** - Too many requests * **500** - Internal server error ### Code examples #### Example **Request:** ```curl curl -L \ -X GET \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups/SCIM_GROUP_ID ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise group](#provision-a-scim-enterprise-group). ## Set SCIM information for a provisioned enterprise group ``` PUT /scim/v2/enterprises/{enterprise}/Groups/{scim_group_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Replaces an existing provisioned group’s information. You must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the Update an attribute for a SCIM enterprise group endpoint instead. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_group_id`** (string) (required) A unique identifier of the SCIM group. * **`enterprise`** (string) (required) The slug version of the enterprise name. #### Body parameters * **`schemas`** (array of strings) (required) The URIs that are used to indicate the namespaces of the SCIM schemas. Supported values are: urn:ietf:params:scim:schemas:core:2.0:Group * **`externalId`** (string) (required) A unique identifier for the resource as defined by the provisioning client. * **`displayName`** (string) (required) A human-readable name for a security group. * **`members`** (array of objects) The group members. * **`value`** (string) (required) The local unique identifier for the member * **`displayName`** (string) (required) The display name associated with the member ### HTTP response status codes * **200** - Group was updated * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **409** - Duplicate record detected * **429** - Too many requests * **500** - Internal server error ### Code examples #### Group **Request:** ```curl curl -L \ -X PUT \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups/SCIM_GROUP_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:Group" ], "externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159", "displayName": "Engineering" }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise group](#provision-a-scim-enterprise-group). #### Group with member **Request:** ```curl curl -L \ -X PUT \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups/SCIM_GROUP_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:Group" ], "externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159", "displayName": "Engineering", "members": [ { "value": "879db59-3bdf-4490-ad68-ab880a2694745", "displayName": "User 1" }, { "value": "0db508eb-91e2-46e4-809c-30dcbda0c685", "displayName": "User 2" } ] }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise group](#provision-a-scim-enterprise-group). ## Update an attribute for a SCIM enterprise group ``` PATCH /scim/v2/enterprises/{enterprise}/Groups/{scim_group_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Update a provisioned group’s individual attributes. To change a group’s values, you must provide a specific Operations JSON format that contains at least one of the add, remove, or replace operations. For examples and more information on the SCIM operations format, see the SCIM specification. Update can also be used to add group memberships. Group memberships can be sent one at a time or in batches for faster performance. Note: The memberships are referenced through a local user id, and the user will need to be created before they are referenced here. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_group_id`** (string) (required) A unique identifier of the SCIM group. * **`enterprise`** (string) (required) The slug version of the enterprise name. #### Body parameters * **`Operations`** (array of objects) (required) patch operations list * **`op`** (string) (required) Can be one of: `add`, `replace`, `remove` * **`path`** (string) * **`value`** (string) Corresponding 'value' of that field specified by 'path' * **`schemas`** (array of strings) (required) undefinedSupported values are: urn:ietf:params:scim:api:messages:2.0:PatchOp ### HTTP response status codes * **200** - Success, group was updated * **204** - No Content * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **409** - Duplicate record detected * **429** - Too many requests * **500** - Internal server error ### Code examples #### Update Group **Request:** ```curl curl -L \ -X PATCH \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups/SCIM_GROUP_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ], "Operations": [ { "op": "replace", "path": "displayName", "value": "Employees" } ] }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise group](#provision-a-scim-enterprise-group). #### Add Members **Request:** ```curl curl -L \ -X PATCH \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups/SCIM_GROUP_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ], "Operations": [ { "op": "add", "path": "members", "value": [ { "value": "879db59-3bdf-4490-ad68-ab880a2694745" }, { "value": "0db508eb-91e2-46e4-809c-30dcbda0c685" } ] } ] }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise group](#provision-a-scim-enterprise-group). ## Delete a SCIM group from an enterprise ``` DELETE /scim/v2/enterprises/{enterprise}/Groups/{scim_group_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Deletes a SCIM group from an enterprise. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_group_id`** (string) (required) A unique identifier of the SCIM group. * **`enterprise`** (string) (required) The slug version of the enterprise name. ### HTTP response status codes * **204** - Group was deleted, no content * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **429** - Too many requests * **500** - Internal server error ### Code examples #### Example **Request:** ```curl curl -L \ -X DELETE \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Groups/SCIM_GROUP_ID ``` **Response schema (Status: 204):** ## List SCIM provisioned identities for an enterprise ``` GET /scim/v2/enterprises/{enterprise}/Users ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Lists provisioned SCIM enterprise members. When a user with a SCIM-provisioned external identity is removed from an enterprise through a patch with active flag set to false, the account's metadata is preserved to allow the user to re-join the enterprise in the future. However, the user's account will be suspended and the user will not be able to sign-in. In order to permanently suspend the users account with no ability to re-join the enterprise in the future, use the delete request. Users that were not permanently deleted will be visible in the returned results. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`filter`** (string) If specified, only results that match the specified filter will be returned. Multiple filters are not supported. Possible filters are userName, externalId, id, and displayName. For example, ?filter=externalId eq "9138790-10932-109120392-12321". * **`startIndex`** (integer) Used for pagination: the starting index of the first result to return when paginating through values. Default: `1` * **`count`** (integer) Used for pagination: the number of results to return per page. Default: `30` * **`enterprise`** (string) (required) The slug version of the enterprise name. ### HTTP response status codes * **200** - Success, either users were found or not found * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **429** - Too many requests * **500** - Internal server error ### Code examples #### Example **Request:** ```curl curl -L \ -X GET \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users ``` **Response schema (Status: 200):** Same response schema as [List provisioned SCIM groups for an enterprise](#list-provisioned-scim-groups-for-an-enterprise). ## Provision a SCIM enterprise user ``` POST /scim/v2/enterprises/{enterprise}/Users ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Creates an external identity for a new SCIM enterprise user. SCIM does not authenticate users, it only provisions them. The authentication of users is done by SAML. However, when SCIM is enabled, all users need to be provisioned through SCIM before a user can sign in through SAML. The matching of a user to a SCIM provisioned user is done when the SAML assertion is consumed. The user will be matched on SAML response NameID to SCIM userName. When converting existing enterprise to use SCIM, the user handle (userName) from the SCIM payload will be used to match the provisioned user to an already existing user in the enterprise. Since the new identity record is created for newly provisioned users the matching for those records is done using a user's handle. Currently the matching will be performed to all of the users no matter if they were SAML JIT provisioned or created as local users. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`enterprise`** (string) (required) The slug version of the enterprise name. #### Body parameters * **`schemas`** (array of strings) (required) The URIs that are used to indicate the namespaces of the SCIM schemas. Supported values are: urn:ietf:params:scim:schemas:core:2.0:User * **`externalId`** (string) (required) A unique identifier for the resource as defined by the provisioning client. * **`active`** (boolean) (required) Whether the user active in the IdP. * **`userName`** (string) (required) The username for the user. * **`name`** (object) * **`formatted`** (string) The full name, including all middle names, titles, and suffixes as appropriate, formatted for display. * **`familyName`** (string) (required) The family name of the user. * **`givenName`** (string) (required) The given name of the user. * **`middleName`** (string) The middle name(s) of the user. * **`displayName`** (string) (required) A human-readable name for the user. * **`emails`** (array of objects) (required) The emails for the user. * **`value`** (string) (required) The email address. * **`type`** (string) (required) The type of email address. * **`primary`** (boolean) (required) Whether this email address is the primary address. * **`roles`** (array of objects) The roles assigned to the user. * **`display`** (string) * **`type`** (string) * **`value`** (string) (required) The role value representing a user role in GitHub. Can be one of: `user`, `27d9891d-2c17-4f45-a262-781a0e55c80a`, `guest_collaborator`, `1ebc4a02-e56c-43a6-92a5-02ee09b90824`, `enterprise_owner`, `981df190-8801-4618-a08a-d91f6206c954`, `ba4987ab-a1c3-412a-b58c-360fc407cb10`, `billing_manager`, `0e338b8c-cc7f-498a-928d-ea3470d7e7e3`, `e6be2762-e4ad-4108-b72d-1bbe884a0f91` * **`primary`** (boolean) Is the role a primary role for the user. ### HTTP response status codes * **201** - User has been created * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **409** - Duplicate record detected * **429** - Too many requests * **500** - Internal server error ### Code examples #### User **Request:** ```curl curl -L \ -X POST \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users \ -d '{ "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "externalId": "E012345", "active": true, "userName": "E012345", "name": { "formatted": "Ms. Mona Lisa Octocat", "familyName": "Octocat", "givenName": "Mona", "middleName": "Lisa" }, "displayName": "Mona Lisa", "emails": [ { "value": "mlisa@example.com", "type": "work", "primary": true } ], "roles": [ { "value": "user", "primary": false } ] }' ``` **Response schema (Status: 201):** * all of: * **object** * `schemas`: required, array of string, enum: `urn:ietf:params:scim:schemas:core:2.0:User` * `externalId`: string or null * `active`: required, boolean * `userName`: string * `name`: object: * `formatted`: string * `familyName`: string * `givenName`: string * `middleName`: string * `displayName`: string or null * `emails`: required, array of objects: * `value`: required, string * `type`: string * `primary`: boolean * `roles`: array of objects: * `display`: string * `type`: string * `value`: required, string, enum: `user`, `27d9891d-2c17-4f45-a262-781a0e55c80a`, `guest_collaborator`, `1ebc4a02-e56c-43a6-92a5-02ee09b90824`, `enterprise_owner`, `981df190-8801-4618-a08a-d91f6206c954`, `ba4987ab-a1c3-412a-b58c-360fc407cb10`, `billing_manager`, `0e338b8c-cc7f-498a-928d-ea3470d7e7e3`, `e6be2762-e4ad-4108-b72d-1bbe884a0f91` * `primary`: boolean * **object** * `id`: required, string * `groups`: array of objects: * `value`: string * `$ref`: string * `display`: string * `meta`: required, object: * `resourceType`: required, string, enum: `User`, `Group` * `created`: string * `lastModified`: string * `location`: string #### Enterprise Owner **Request:** ```curl curl -L \ -X POST \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users \ -d '{ "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "externalId": "E012345", "active": true, "userName": "E012345", "name": { "formatted": "Ms. Mona Lisa Octocat", "familyName": "Octocat", "givenName": "Mona", "middleName": "Lisa" }, "displayName": "Mona Lisa", "emails": [ { "value": "mlisa@example.com", "type": "work", "primary": true } ], "roles": [ { "value": "enterprise_owner", "primary": false } ] }' ``` **Response schema (Status: 201):** * all of: * **object** * `schemas`: required, array of string, enum: `urn:ietf:params:scim:schemas:core:2.0:User` * `externalId`: string or null * `active`: required, boolean * `userName`: string * `name`: object: * `formatted`: string * `familyName`: string * `givenName`: string * `middleName`: string * `displayName`: string or null * `emails`: required, array of objects: * `value`: required, string * `type`: string * `primary`: boolean * `roles`: array of objects: * `display`: string * `type`: string * `value`: required, string, enum: `user`, `27d9891d-2c17-4f45-a262-781a0e55c80a`, `guest_collaborator`, `1ebc4a02-e56c-43a6-92a5-02ee09b90824`, `enterprise_owner`, `981df190-8801-4618-a08a-d91f6206c954`, `ba4987ab-a1c3-412a-b58c-360fc407cb10`, `billing_manager`, `0e338b8c-cc7f-498a-928d-ea3470d7e7e3`, `e6be2762-e4ad-4108-b72d-1bbe884a0f91` * `primary`: boolean * **object** * `id`: required, string * `groups`: array of objects: * `value`: string * `$ref`: string * `display`: string * `meta`: required, object: * `resourceType`: required, string, enum: `User`, `Group` * `created`: string * `lastModified`: string * `location`: string ## Get SCIM provisioning information for an enterprise user ``` GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Gets information about a SCIM user. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_user_id`** (string) (required) The unique identifier of the SCIM user. * **`enterprise`** (string) (required) The slug version of the enterprise name. ### HTTP response status codes * **200** - Success, a user was found * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **429** - Too many requests * **500** - Internal server error ### Code examples #### Example **Request:** ```curl curl -L \ -X GET \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users/SCIM_USER_ID ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise user](#provision-a-scim-enterprise-user). ## Set SCIM information for a provisioned enterprise user ``` PUT /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Replaces an existing provisioned user's information. You must provide all the information required for the user as if you were provisioning them for the first time. Any existing user information that you don't provide will be removed. If you want to only update a specific attribute, use the Update an attribute for a SCIM user endpoint instead. Warning Setting active: false will suspend a user and obfuscate the user handle and user email. Since the implementation is a generic SCIM implementation and does not differentiate yet between different IdP providers, for Okta, the user GDPR data will not be purged and the credentials will not be removed. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_user_id`** (string) (required) The unique identifier of the SCIM user. * **`enterprise`** (string) (required) The slug version of the enterprise name. #### Body parameters * **`schemas`** (array of strings) (required) The URIs that are used to indicate the namespaces of the SCIM schemas. Supported values are: urn:ietf:params:scim:schemas:core:2.0:User * **`externalId`** (string) (required) A unique identifier for the resource as defined by the provisioning client. * **`active`** (boolean) (required) Whether the user active in the IdP. * **`userName`** (string) (required) The username for the user. * **`name`** (object) * **`formatted`** (string) The full name, including all middle names, titles, and suffixes as appropriate, formatted for display. * **`familyName`** (string) (required) The family name of the user. * **`givenName`** (string) (required) The given name of the user. * **`middleName`** (string) The middle name(s) of the user. * **`displayName`** (string) (required) A human-readable name for the user. * **`emails`** (array of objects) (required) The emails for the user. * **`value`** (string) (required) The email address. * **`type`** (string) (required) The type of email address. * **`primary`** (boolean) (required) Whether this email address is the primary address. * **`roles`** (array of objects) The roles assigned to the user. * **`display`** (string) * **`type`** (string) * **`value`** (string) (required) The role value representing a user role in GitHub. Can be one of: `user`, `27d9891d-2c17-4f45-a262-781a0e55c80a`, `guest_collaborator`, `1ebc4a02-e56c-43a6-92a5-02ee09b90824`, `enterprise_owner`, `981df190-8801-4618-a08a-d91f6206c954`, `ba4987ab-a1c3-412a-b58c-360fc407cb10`, `billing_manager`, `0e338b8c-cc7f-498a-928d-ea3470d7e7e3`, `e6be2762-e4ad-4108-b72d-1bbe884a0f91` * **`primary`** (boolean) Is the role a primary role for the user. ### HTTP response status codes * **200** - User was updated * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **409** - Duplicate record detected * **429** - Too many requests * **500** - Internal server error ### Code examples #### User **Request:** ```curl curl -L \ -X PUT \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users/SCIM_USER_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "externalId": "E012345", "active": true, "userName": "E012345", "name": { "formatted": "Ms. Mona Lisa Octocat", "familyName": "Octocat", "givenName": "Mona", "middleName": "Lisa" }, "displayName": "Mona Lisa", "emails": [ { "value": "mlisa@example.com", "type": "work", "primary": true } ], "roles": [ { "value": "user", "primary": false } ] }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise user](#provision-a-scim-enterprise-user). ## Update an attribute for a SCIM enterprise user ``` PATCH /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Update a provisioned user's individual attributes. To change a user's values, you must provide a specific Operations JSON format that contains at least one of the add, remove, or replace operations. For examples and more information on the SCIM operations format, see the SCIM specification. Note Complicated SCIM path selectors that include filters are not supported. For example, a path selector defined as "path": "emails\[type eq "work"]" will not work. Warning Setting active: false will suspend a user and obfuscate the user handle and user email. Since the implementation is a generic SCIM implementation and does not differentiate yet between different IdP providers (Okta, for example), the user GDPR data in the SCIM metadata will not be purged and the credentials will not be removed. { "Operations":\[{ "op":"replace", "value":{ "active":false } }] } ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_user_id`** (string) (required) The unique identifier of the SCIM user. * **`enterprise`** (string) (required) The slug version of the enterprise name. #### Body parameters * **`Operations`** (array of objects) (required) patch operations list * **`op`** (string) (required) Can be one of: `add`, `replace`, `remove` * **`path`** (string) * **`value`** (string) Corresponding 'value' of that field specified by 'path' * **`schemas`** (array of strings) (required) undefinedSupported values are: urn:ietf:params:scim:api:messages:2.0:PatchOp ### HTTP response status codes * **200** - Success, user was updated * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **409** - Duplicate record detected * **429** - Too many requests * **500** - Internal server error ### Code examples #### Multi Valued Property **Request:** ```curl curl -L \ -X PATCH \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users/SCIM_USER_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ], "Operations": [ { "op": "replace", "path": "emails[type eq 'work'].value", "value": "updatedEmail@microsoft.com" }, { "op": "replace", "path": "name.familyName", "value": "updatedFamilyName" } ] }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise user](#provision-a-scim-enterprise-user). #### Single Valued Property **Request:** ```curl curl -L \ -X PATCH \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users/SCIM_USER_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ], "Operations": [ { "op": "replace", "path": "userName", "value": "5b50642d-79fc-4410-9e90-4c077cdd1a59@testuser.com" }, { "op": "replace", "path": "displayName", "value": "Monalisa Octocat" } ] }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise user](#provision-a-scim-enterprise-user). #### Disable User **Request:** ```curl curl -L \ -X PATCH \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users/SCIM_USER_ID \ -d '{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ], "Operations": [ { "op": "replace", "path": "active", "value": false } ] }' ``` **Response schema (Status: 200):** Same response schema as [Provision a SCIM enterprise user](#provision-a-scim-enterprise-user). ## Delete a SCIM user from an enterprise ``` DELETE /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} ``` Note The SCIM API endpoints for enterprise accounts are currently in private preview and are subject to change. Permanently suspends a SCIM user from an enterprise, removes all data for the user, obfuscates the login, email, and display name of the user, removes all external-identity SCIM attributes, and deletes the emails, avatar, PATs, SSH keys, OAuth authorizations credentials, GPG keys, and SAML mappings for the user. You will not be able to undo this action. ### Parameters #### Headers * **`accept`** (string) Setting to `application/vnd.github+json` is recommended. #### Path and query parameters * **`scim_user_id`** (string) (required) The unique identifier of the SCIM user. * **`enterprise`** (string) (required) The slug version of the enterprise name. ### HTTP response status codes * **204** - User was deleted, no content * **400** - Bad request * **401** - Authorization failure * **403** - Permission denied * **404** - Resource not found * **429** - Too many requests * **500** - Internal server error ### Code examples #### Example **Request:** ```curl curl -L \ -X DELETE \ http(s)://HOSTNAME/api/v3/scim/v2/enterprises/ENTERPRISE/Users/SCIM_USER_ID ``` **Response schema (Status: 204):**