Integrations (v1)
Last updated
Last updated
More information
Snyk privacy policy© 2024 Snyk Limited | All product and company names and logos are trademarks of their respective owners.
View Organization
View Integrations
Edit Integrations
Removes any credentials set for this integration. If this is a brokered connection the operation will have no effect.
The organization ID. The API_KEY
must have access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
The integration ID.
"4a18d42f-0706-4ad0-b127-24078731fbed"
Switch the existing broker token with the provisioned token for this integration and any other in the same group. Only perform this action when you have a Broker client running with the provisioned token. This action will fail if there is no token provisioned for this integration or any integration in the same group.
View Organization
View Integrations
Edit Integrations
The API_KEY
must have access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
"4a18d42f-0706-4ad0-b127-24078731fbed"
View Organization
View Integrations
The organization public ID. The API_KEY
must have admin access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
Issue a new and unique provisional broker token for the brokered integration.
Used for zero down-time token rotation with the Snyk Broker. Once provisioned, the token can be used to initialize a new broker client before using the switch API to update the token in use by the integration.
The new provisional token will fail to be created if the integration, or any other integration in the same group, already has one provisioned.
View Organization
View Integrations
Edit Integrations
The API_KEY
must have access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
"4a18d42f-0706-4ad0-b127-24078731fbed"
View Organization
- View Integrations
The API_KEY
must have admin access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
Integration type.
Alphanumeric UUID including - with a limit of 36 characters
Clone an integration, including all of its settings and credentials from one organization to another organization in the same group. This API supports both brokered and non-brokered integrations.
Use this API for when you want to share a Broker token between several Snyk organizations (integrations).
View Organization
View Integrations
Edit Integrations
Source organization public ID to clone integration settings from. The API_KEY
must have access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
Source integration public ID to clone.
"4a18d42f-0706-4ad0-b127-24078731fbed"
The organization public ID. The API_KEY
must have access to this organization.
Add new integration for given organization.
View Organization
View Integrations
Edit Integrations
The organization ID. The API_KEY
must have admin access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
View Organization
View Integrations
The organization ID. The API_KEY
must have admin access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
The unique identifier for the configured integration. This can be found on the Integration page in the Settings area for all integrations that have been configured.
"9a3e5d90-b782-468a-a042-9a2073736f0b"
A limit on how many automatic dependency upgrade PRs can be opened simultaneously
A list of strings defining what dependencies should be ignored
Defines if the functionality is enabled
The age (in days) that an automatic dependency check is valid for
If an opened PR should fail to be validated if any vulnerable dependencies have been detected
If an opened PR only should fail its validation if any dependencies are marked as being of high severity
If opened PRs should be tested
assign Snyk pull requests
If true, will automatically detect and scan Dockerfiles in your Git repositories, surface base image vulnerabilities and recommend possible fixes
Update integration's credentials for given organization. Integration must be not brokered
Enable or disable brokered integration for given organization. Credentials required for disabling brokered integration
Examples in right section:
Set up a broker for an existing integration
Update credentials for an existing non-brokered integration
Disable broker for an existing integration
View Organization
View Integrations
Edit Integrations
The organization ID. The API_KEY
must have admin access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
The unique identifier for the configured integration. This can be found on the Integration page in the Settings area for all integrations that have been configured.
"9a3e5d90-b782-468a-a042-9a2073736f0b"
View Organization
View Integrations
Edit Integrations
The organization ID. The API_KEY
must have admin access to this organization.
"4a18d42f-0706-4ad0-b127-24078731fbed"
The unique identifier for the configured integration. This can be found on the Integration page in the Settings area for all integrations that have been configured.
"9a3e5d90-b782-468a-a042-9a2073736f0b"
A limit on how many automatic dependency upgrade PRs can be opened simultaneously
A list of strings defining what dependencies should be ignored
Defines if the functionality is enabled
The age (in days) that an automatic dependency check is valid for
If an opened PR should fail to be validated if any vulnerable dependencies have been detected
If an opened PR only should fail its validation if any dependencies are marked as being of high severity
If opened PRs should be tested
assign Snyk pull requests
If true, will automatically detect and scan Dockerfiles in your Git repositories, surface base image vulnerabilities and recommend possible fixes
A limit on how many automatic dependency upgrade PRs can be opened simultaneously
A list of strings defining what dependencies should be ignored
Defines if the functionality is enabled
The age (in days) that an automatic dependency check is valid for
If an opened PR should fail to be validated if any vulnerable dependencies have been detected
If an opened PR only should fail its validation if any dependencies are marked as being of high severity
If opened PRs should be tested
assign Snyk pull requests
If true, will automatically detect and scan Dockerfiles in your Git repositories, surface base image vulnerabilities and recommend possible fixes