Now that you have your environment ID from step 1 and your integration and version IDs from step 2, it’s time to download the integration kit. Using this information, your endpoint becomes {{apiPath}}/environments/{{envID}}/integrations/{{integrationID}}/versions/{{integrationVersionID}}/asset, where {{integrationID}} is c290da08-0151-45f6-a651-0efg0805ca34 and {{integrationVersionID}} is a9c8a539-191e-4015-ab52-c1943d2142a1 (from step 2).

When you call the endpoint, the PingOne API will generate and redirect to a presigned URL with a short expiration that will automatically download the file. The zip file will have the following naming convention: {{integration-name}}-{{integration-version}}.zip. The response will include an x-amz-meta-etag header with a sha256 hash for any integrity checks you may want to perform. The value will be in the form “sha256={{sha256 hash value}}”.