Step 4: Download the integration zip file

GET {{apiPath}}/environments/{{envID}}/integrations/{{integrationID}}/versions/{{integrationVersionID}}/asset

Now that you have your integration and version IDs from steps 2 and 3, it's time to download the integration kit.

When you call the {{apiPath}}/environments/{{envID}}/integrations/{{integrationID}}/versions/{{integrationVersionID}}/asset endpoint, the PingOne API generates and redirects 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}}.

Note: There is a 50 MB size limit for integration downloads.

HEADERS

KeyDatatypeRequiredDescription
Authorizationstring