Users service


Users

A user resource is a unique identity within PingOne that interacts with the applications and services in the environment to which the user is assigned. The users service implements directory functions to create, read, update, delete, and search for user resources. Users are associated with an environment and a population. The following diagram shows how users are organized in the directory.

Users

The examples below show common actions to find and manage users. You need the Identity Data Admin role to perform operations on users resources.

Filtering result data

You can filter result data by applying a SCIM filtering expression to the GET request URL. For large collections, a filtering expression appended to the query returns a targeted, more useful data set. For example, this URL-encoded SCIM filter returns users with a last name of “Smith” and a first name that starts with the letter “W”:

https://api.pingone.com/v1/environments/b7372995-824b-44ff-99f8-ab151dac3263/users?filter=name.family%20eq%20%Smith%22%20and%20name.given%20sw%20%22W%22"

These SCIM operators can be applied to the following attributes:

  • eq (equals)

    Supported attributes: username, name.family, name.given, email, mobilePhone, population.id

  • sw (starts with)

    Supported attributes: username, name.family, name.given, email, mobilePhone

  • and (logical AND)

    Logical AND for building compound expressions in which both expressions are true.

  • or (logical OR)

    Logical OR for building compound expressions if either expression is true.

Note: These SCIM operators are not supported: ne (not equal), co (contains), ew (ends with), pr (present, is a non-empty or non-null value), gt (greater than), ge (greater than or equal to), lt (less than), le (less than or equal to), not (logical NOT).

For more information about SCIM syntax and operators, see Conventions.

Users API operations

The users service supports the following endpoint operations:

For hands-on experience with the users API endpoints, click the Run in Postman button below to download a Postman collection that you can import and open in your local Postman application.

Users data model

Property Description
account.secondsUntilLockout The number of seconds until the user’s password is unlocked (only present if the account is locked).
account.warnings An array of account warnings, if applicable.
accountId A string that specifies the user’s account ID, which is optional. This may be explicitly set to null when updating a user to unset it. This attribute is organization-specific and has no special meaning within the PingOne platform.
address.countryCode A string that specifies the country name component. When specified, the value must be in ISO 3166-1 “alpha-2” code format [ISO3166]. For example, the country codes for the United States and Sweden are “US” and “SE”, respectively.
address.locality A string that specifies the city or locality component of the address.
address.postalCode A string that specifies the zip code or postal code component of the address.
address.region A string that specifies the state or region component of the address.
address.streetAddress A string that specifies the full street address component, which may include house number, street name, P.O. box, and multi-line extended street address information. This attribute may contain newlines.
createdAt The time the resource was created.
email A string that specifies the user’s email address, which must be provided and valid.
enabled A read-only boolean attribute that specifies whether the user is enabled. This attribute is set to ‘true’ by default when the user is created.
environment.id A string that specifies the environment resource’s unique identifier associated with the user.
externalId A string that specifies an identifier for the user resource as defined by the provisioning client. This is optional. This may be explicitly set to null when updating a user to unset it. The externalId attribute may simplify the correlation of the user in PingOne with the user’s account in another system of record. The platform does not use this attribute directly in any way, but it is used by Ping Identity’s Data Sync product.
id A string that specifies the user resource’s unique identifier.
locale A string that specifies the user’s default location, which is optional. This may be explicitly set to null when updating a user to unset it. This is used for purposes of localizing such items as currency, date time format, or numerical representations. If provided, a valid value is a language tag as defined in RFC 5646. The following are example tags: fr, en-US, es-419, az-Arab, man-Nkoo-GN.
mfaEnabled A read-only boolean attribute that specifies whether multi-factor authentication is enabled. This attribute is set to ‘false’ by default when the user is created.
mobilePhone A string that specifies the user’s mobile phone number, which is optional. This might also match the primaryPhone attribute. This may be explicitly set to null when updating a user to unset it. If provided, it must consist of a leading plus sign, 1 to 3-digit country code, dot separator, 4 to 14-digit phone number, and optional 1 to 8-digit extension (for example, +1.3034682900x1234).
name.family A string that specifies the family name of the user, or Last in most Western languages (for example, ‘Jensen’ given the full name ‘Ms. Barbara J Jensen, III’). This may be explicitly set to null when updating a name to unset it. Valid characters consists of any Unicode letter, mark (for example, accent, umlaut), space, dot, apostrophe, or hyphen. It can have a length of no more than 256 characters.
name.formatted A string that specifies the fully formatted name of the user (for example ‘Ms. Barbara J Jensen, III’). This can be explicitly set to null when updating a name to unset it.
name.given A string that specifies the given name of the user, or First in most Western languages (for example, ‘Barbara’ given the full name ‘Ms. Barbara J Jensen, III’). This may be explicitly set to null when updating a name to unset it. Valid characters consists of any Unicode letter, mark (for example, accent, umlaut), space, dot, apostrophe, or hyphen. It can have a length of no more than 256 characters.
name.honorificPrefix A string that specifies the honorific prefix(es) of the user, or title in most Western languages (for example, ‘Ms.’ given the full name ‘Ms. Barbara Jane Jensen, III’). This can be explicitly set to null when updating a name to unset it.
name.honorificSuffix A string that specifies the honorific suffix(es) of the user, or suffix in most Western languages (for example, ‘III’ given the full name ‘Ms. Barbara Jane Jensen, III’). This can be explicitly set to null when updating a name to unset it.
name.middle A string that specifies the the middle name(s) of the user (for exmple, ‘Jane’ given the full name ‘Ms. Barbara Jane Jensen, III’). This can be explicitly set to null when updating a name to unset it. Valid characters consists of any Unicode letter, mark (for example, accent, umlaut), space, dot, apostrophe, or hyphen. It can have a length of no more than 256 characters.
nickname A string that specifies the user’s nickname, which is optional. This can be explicitly set to null when updating a user to unset it. Valid characters consists of any Unicode letter, mark (for example, accent, umlaut), space, dot, apostrophe, or hyphen. It can have a length of no more than 256 characters.
photo.href A string that specifies the URI that is a uniform resource locator (as defined in Section 1.1.3 of RFC 3986) that points to a resource location representing the user’s image. This can be removed from a user by setting the photo attribute to null. If provided, the resource must be a file (for example, a GIF, JPEG, or PNG image file) rather than a web page containing an image. It must also have a scheme of HTTP or HTTPS.
population.id A string that specifies the identifier of the population resource associated with the user.
preferredLanguage A string that specifies the user’s preferred written or spoken languages, which are optional. This may be explicitly set to null when updating a user to unset it. If provided, the format of the value is the same as the HTTP Accept-Language header field (not including Accept-Language:) and is specified in Section 5.3.5 of RFC 7231. For example: en-US, en-gb;q=0.8, en;q=0.7.
primaryPhone A string that specifies the user’s primary phone number, which is optional. This might also match the mobilePhone attribute. This may be explicitly set to null when updating a user to unset it. If provided, it must consist of a leading plus sign, 1 to 3-digit country code, dot separator, 4 to 14-digit phone number, and optional 1 to 8-digit extension (for example, +1.3034682900x1234).
timezone A string that specifies the user’s time zone, which is optional. This can be explicitly set to null when updating a user to unset it. If provided, it must conform with the IANA Time Zone database format [RFC6557], also known as the “Olson” time zone database format [Olson-TZ] for example, “America/Los_Angeles”).
title A string that specifies the user’s title, which is optional, such as “Vice President”. This can be explicitly set to null when updating a user to unset it.
type A string that specifies the user’s type, which is optional. This can be explicitly set to null when updating a user to unset it. This attribute is organization-specific and has no special meaning within the PingOne platform. It could have values of “Contractor”, “Employee”, “Intern”, “Temp”, “External”, and “Unknown”.
updatedAt The time the resource was last updated.
username A string that specifies the user name, which must be provided and must be unique within an environment. The username must either be a well-formed email address or a string of any Unicode letter, mark (for example, accent, umlaut), dot, underscore, or hyphen. It can have a length of no more than 128 characters.

Response codes

Code Message
200 Successful operation.
201 Successfully created.
204 Successfully removed. No content.
400 The request was invalid.
401 You are not authenticated to perform this operation.
404 The specified object doesn’t exist.
409 Uniqueness constraint violation.

Endpoint examples

Get users

The following sample shows the GET /environments/{environmentId}/users operation to return a list of all user resources for the specified environment.

curl -X "GET" "https://api.pingone.com/v1/environments/{environmentId}/users" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken'

The response data looks like this:

{
  "_links" : {
    "self" : {
      "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users"
    }
  },
  "_embedded" : {
    "users" : [ {
      "_links" : {
        "self" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0"
        },
        "password" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
        },
        "password.set" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
        },
        "password.reset" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
        }
        "password.validate": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
      },
      "id" : "9a774ad6-b6b6-4179-af87-226cd68955f0",
      "environment" : {
        "id" : "02d37832-476a-431b-8a60-d77cecd7005c"
      },
      "population" : {
        "id" : "7c686ee8-a0cc-4c6f-8336-a37bb0384acd"
      },
      "username" : "Joe",
      "email" : "joe@ping.com",
      "createdAt" : "2018-05-15T19:23:25.089Z",
      "updatedAt" : "2018-05-15T19:23:25.089Z"
    }, {
      "_links" : {
        "self" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/3987b40b-c4f9-4c3a-9c23-8b957c8cfced"
        },
        "password" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/3987b40b-c4f9-4c3a-9c23-8b957c8cfced/password"
        },
        "password.set" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/3987b40b-c4f9-4c3a-9c23-8b957c8cfced/password"
        },
        "password.reset" : {
          "href" : "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/3987b40b-c4f9-4c3a-9c23-8b957c8cfced/password"
        }
        "password.validate": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
      },
      "id" : "3987b40b-c4f9-4c3a-9c23-8b957c8cfced",
      "environment" : {
        "id" : "02d37832-476a-431b-8a60-d77cecd7005c"
      },
      "population" : {
        "id" : "c47e0d4e-10c9-4589-9046-6652e014a786"
      },
      "username" : "ashley_graham",
      "name" : {
        "family" : "graham",
        "given" : "ashley"
      },
      "email" : "do-not-send@pingidentity.com",
      "createdAt" : "2018-06-01T19:44:21.780Z",
      "updatedAt" : "2018-06-01T19:44:21.780Z"
    } ]
  },
  "count" : 2,
  "size" : 2
}

Get one user

To get data for a single user resource, the GET /environments/{environmentId}/users/{userId} operation returns data only for the user resource with the ID specified in the request URL.

curl -X GET "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}" \
-H "Content-type: application/json" \
-H "Authorization: Bearer jwtToken"

The response data looks like this:

{
    "_links": {
        "self": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0"
        },
        "environment": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c"
        },
        "population": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/populations/7c686ee8-a0cc-4c6f-8336-a37bb0384acd"
        },
        "password": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
        },
        "password.reset": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
        },
        "password.set": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
        },
        "password.validate": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/password"
        }
    },
    "id": "9a774ad6-b6b6-4179-af87-226cd68955f0",
    "environment": {
        "id": "02d37832-476a-431b-8a60-d77cecd7005c"
    },
    "population": {
        "id": "7c686ee8-a0cc-4c6f-8336-a37bb0384acd"
    },
    "account": {
        "warnings": [
            "USER_DISABLED",
            "MUST_CHANGE_PASSWORD"
        ]
    },
    "createdAt": "2018-05-15T19:23:25.089Z",
    "email": "joe@ping.com",
    "enabled": false,
    "mfaEnabled": false,
    "updatedAt": "2018-08-06T19:22:43.671Z",
    "username": "Joe"
}

Create users

The following sample shows the POST /environments/{environmentId}/users operation to add a new user resource to the specified environment. This operation creates a new user but does not support an attribute to set the new user’s password. To create a user and set the password, see Import users.

curl -X "POST" "https://api.pingone.com/v1/environments/{environmentId}/users" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
  "username": "lindajones",
  "email": "ljones@company.com",
  "population" : {
    "id" : "21731b50-6b54-41b0-8454-9cd9de62a7a1"
    }
}'

New users must be assigned to a population resource identified by its ID, and the request must set values for the username and email attributes. If successful, the response returns a 201 Successfully created message and shows the new user resource’s property data.

Note: For information about setting a user’s password after creating the new user, see Set password.

Import users

The import users operation gives privileged applications the ability to create a new user and set the user’s password. The password attribute in this operation uses the same format for specifying passwords as the set password request, allowing both cleartext and pre-encoded password values. This endpoint requires the dir:import:user permission, which is not included in the Identity Data Admin role (or any other administrator role).

The following sample shows the POST /environments/{environmentId}/users operation to import a new user resource to the specified environment. This operation uses the application/vnd.pingidentity.user.import+json custom content type in the request header.

curl -X "POST" "https://api.pingone.com/v1/environments/{environmentId}/users" \
-H 'Content-type: application/vnd.pingidentity.user.import+json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
  "email":"angelamontero@pingidentity.com",
  "name":{  
     "given":"angela",
     "family":"montero"
  },
  "population":{  
     "id":"87972995-664b-11ff-99f8-qw341dac3667"
  },
  "username":"angelamontero",
  "password":{
     "value": "{SSHA512}UkGWfORubNKFpFBWh+Lgy4FrciclzUXneuryV+B+zBDR4Gqd5wvMqAvKRixgQWoZlZUgq8Wh40uMK3s6bWpzWt1/TqQH02hX",
     "forceChange": false
  }
 }'

New users must be assigned to a population resource identified by its ID, and the request must set values for the username and email attributes. In addition, this operation supports the password attribute, which can accept a pre-encoded password value and a forceChange value of false. If successful, the response returns a 201 Successfully created message and shows the new user resource’s property data.

Note: Pre-encoded passwords are specified by the name of the encoding scheme followed by an encoded representation of the password (as shown in the example above). Supported encoding schemes are bcrypt, scrypt, salted SHA1, salted SHA256, salted SHA384, and salted SHA512.

For more information about pre-encoded passwords, see Set password. For import operations, if a pre-encoded password is not accepted by PingOne, then it does not conform to the supported encoding schemes described in the Set password topic.

Update users

You can use the PUT /environments/{environmentId}/users/{userId} operation to update existing attribute properties. For PUT requests, the update operation removes any existing attribute property values omitted from the request body.

curl -X "PUT" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
    "username": "joe@example.com",
    "name": {
        "formatted": "Joe Smith",
        "given": "Joe",
        "middle": "H.",
        "family": "Smith",
        "honorificPrefix": "Dr.",
        "honorificSuffix": "IV"
    },
    "nickname": "Putty",
    "title": "Senior Director",
    "preferredLanguage": "en-gb;q=0.8, en;q=0.7",
    "locale": "en-gb",
    "email": "joe@example.com",
    "primaryPhone": "+1.2225554444",
    "mobilePhone": "+1.4445552222",
    "photo": {
        "href": "<url-to-image>"
    },
    "address": {
        "streetAddress": "123 Main Street",
        "locality": "Springfield",
        "region": "WA",
        "postalCode": "98701",
        "countryCode": "US"
    },
    "accountId": "5",
    "type": "tele",
    "timezone": "America/Los_Angeles"
}'

The response data shows the updates for all attribute values specified in the request body.

Partial update

The following sample shows the PATCH /environments/{environmentId}/users/{userId} operation to update existing attribute properties. For the PATCH operation, the update operation targets only those attribute values specified in the request body. Attributes omitted from the request body are not updated or removed.

curl -X "PATCH" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
    "username": "joesmith@example.com",
    "email": "joesmith@example.com"
}'

Get user enabled setting

When a new user resource is created, the value specified for the enabled attribute determines the user’s ability to authenticate. If the enabled attribute is omitted from the POST request, the value is set to true by default.

For existing users, you can use the GET /environments/{environmentId}/users/{userId}/enabled operation to check whether the specified user is enabled or disabled.

curl -X "GET" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}/enabled" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken'

The response data for an enabled user looks like this:

{
    "_links": {
        "self": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/enabled"
        },
        "user": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0"
        }
    },
    "enabled": true
}

Update user enabled setting

You can modify the user’s enabled attribute value by calling the PUT /environments/{environmentId}/users/{userId}/enabled endpoint.

The following sample shows the PUT /environments/{environmentId}/users/{userId}/enabled operation to disable the user resource’s ability to authenticate.

curl -X "PUT" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}/enabled" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
  "enabled": "false"
}'

The response data with the updated setting looks like this:

{
    "_links": {
        "self": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/enabled"
        },
        "user": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0"
        }
    },
    "enabled": false
}

Get MFA enabled setting

When a new user resource is created, the mfaEnabled attribute that controls the user’s ability to use multi-factor authentication is set to false by default.

For existing users, you can use the GET /environments/{environmentId}/users/{userId}/mfaEnabled operation to check whether the specified user is enabled or disabled.

curl -X "GET" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}/mfaEnabled" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken'

The response data looks like this:

{
  "_links": {
    "self": {
      "href": "https://api.pingone.com/v1/environments/b7372995-824b-44ff-99f8-ab151dac3263/users/05ad3cc6-8723-4f85-9711-05ad549717f6/mfaEnabled"
    },
    "user": {
      "href": "https://api.pingone.com/v1/environments/b7372995-824b-44ff-99f8-ab151dac3263/users/05ad3cc6-8723-4f85-9711-05ad549717f6"
    }
  },
  "mfaEnabled": false
}

Update MFA enabled setting

The mfaEnabled attribute is a read-only attribute that cannot be changed through calls to PUT /environments/{environmentId}/users/{userId} or PATCH /environments/{environmentId}/users/{userId}. However, you can update the mfaEnabled value by calling the PUT /environments/{environmentId}/users/{userId}/mfaEnabled endpoint.

The following sample shows the PUT /environments/{environmentId}/users/{userId}/mfaEnabled operation to enable the user resource’s ability to use multi-factor authentication.

curl -X "PUT" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}/mfaEnabled" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
   "mfaEnabled": "true"
}'

The response returns a 200 OK message. The response data looks like this:

{
  "_links": {
    "self": {
      "href": "https://api.pingone.com/v1/environments/b7372995-824b-44ff-99f8-ab151dac3263/users/05ad3cc6-8723-4f85-9711-05ad549717f6/mfaEnabled"
    },
    "user": {
      "href": "https://api.pingone.com/v1/environments/b7372995-824b-44ff-99f8-ab151dac3263/users/05ad3cc6-8723-4f85-9711-05ad549717f6"
    }
  },
  "mfaEnabled": true
}

Verify users

The verified property indicates whether the user has been verified through email or sms. When a user resource is created, the verified property can be set to true or false; the property defaults to false if it is omitted from the POST request. If false, a verification code is sent to the email address provided in the user resource’s email property to verify the account.

The following sample shows the POST /environments/{envId}/users/{userId} operation to send a verification email with a verification code to an unverified user. This operation uses the application/vnd.pingidentity.user.verify+json custom content type in the request header.

curl -X "POST" "https://api.pingone.com/v1/environments/{envId}/users/{userId}" \
-H 'Content-type: application/vnd.pingidentity.user.verify+json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
  "verificationCode": <code>
}'

If the user loses or did not receive the verification code, a new verification code can be sent using the POST /environments/{envId}/users/{userId} operation. For the code resend operation, the application/vnd.pingidentity.user.sendVerificationCode+json custom content type is required in the request header.

curl -X "POST" "https://api.pingone.com/v1/environments/{envId}/users/{userId}" \
-H 'Content-type: application/vnd.pingidentity.user.sendVerificationCode+json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
  "verificationCode": <code>
}'

Get user population setting

To get the population ID associated with a single user resource, the GET /environments/{environmentId}/users/{userId}/population operation returns the population setting for the user resource with the ID specified in the request URL.

curl -X GET "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}/population" \
-H "Content-type: application/json" \
-H "Authorization: Bearer jwtToken"

The response data looks like this:

{
    "_links": {
        "self": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0/population"
        },
        "user": {
            "href": "https://api.pingone.com/v1/environments/02d37832-476a-431b-8a60-d77cecd7005c/users/9a774ad6-b6b6-4179-af87-226cd68955f0"
        }
    },
    "id": "7c686ee8-a0cc-4c6f-8336-a37bb0384acd"
}

Update user population setting

To move a user from one population to another, you need to know the ID of the new population resource to associate with the user. To retrieve the list of all population IDs for a specified environment, you can call the GET /environments/{environmentId}/populations method.

The following sample shows the PUT /environments/{environmentId}/users/{userId}/population operation to associate the user with the different population.

curl -X "PUT" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}/population" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken' \
-d $'{
  "id": "21731b50-6b54-41b0-8454-9cd9de62a7a1"
}'

In the request body, the id attribute value is the population ID for the new population to associate with the user.

Delete users

To delete a user resource from the directory, you need to specify the environment and user IDs.

The following sample shows the DELETE /environments/{environmentId}/users/{userId} operation to remove the specified user resource from the directory.

curl -X "DELETE" "https://api.pingone.com/v1/environments/{environmentId}/users/{userId}" \
-H 'Content-type: application/json' \
-H 'Authorization: Bearer jwtToken'

For successful delete operations, a 204 NO CONTENT message is returned by the request.