Import Projects (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.
Request a target to be analyzed for supported Snyk projects via a configured integration. See the Integrations API to configure a new integration.
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"
Note: Importing targets through a Github (Cloud) integration requires the use of a Snyk personal access/api token.
an array of file objects
a comma-separated list of up to 10 folder names to exclude from scanning (each folder name must not exceed 100 characters). If not specified, it will default to "fixtures, tests, __tests__, node_modules". If an empty string is provided - no folders will be excluded. This attribute is only respected with Open Source and Container scan targets.
Note: Importing targets through a Github (Cloud) integration requires the use of a Snyk personal access/api token.
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"
The ID of the job. This can be found in the Location response header from the corresponding POST request that triggered the import job.
"1a325d9d-b782-468a-a242-9a2073734f0b"
A uuid representing the job's id
a string representing the status of a job.
One of: pending, failed, aborted or complete.
the time when an import job was created represented as a UTC (ISO-8601) string
all organizations imported by the job