Now that you have the environment ID, you need to retrieve a list of integrations associated with that environment. Each integration can have several versions, so you may need to further filter your results to return a more manageable list.

For the purpose of this example, we will assume that you cannot remember the name of the integration kit, but your certain “PingID” was part of it. You want to download the latest version of the integration kit, so you also want to set the expand attribute to latestVersion. Your endpoint becomes {apiPath}/environments/{envID}/integrations?expand=latestVersion&filter=(name co "PingID"), where {envID} equals 020ed26b-ae15-4783-8fb3-gd65816dc391 (from step 1). The filter attribute limits the response to those integrations that contain case-insensitive value of “pingid”. See the PingOne API reference for all filtering options.

The example response to the right (or below) contains the information we want. For the purpose of this exercise, we will assume the first integration is the one we want. Looking at the object, we can see that our integration ID is c290da08-0151-45f6-a651-0efg0805ca34 and the version ID is a9c8a539-191e-4015-ab52-c1943d2142a1.