Snyk

Manage projects, issues, and vulnerability scanning via the Snyk API.

Detail	Value
Category	Security
Base URL	https://api.snyk.io/rest
Authentication	API Key
Endpoints	5
Connector key	snyk

Using Snyk in a workflow

1. Go to Connections and click New Connection.
2. Pick Snyk from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /orgs	List organizations
GET /orgs/{orgId}/projects	List projects
GET /orgs/{orgId}/issues	List issues
GET /orgs/{orgId}/targets	List targets
GET /self	Get current user

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /orgs

List organizations

Detail	Value
Operation ID	security.listOrgs
Method	GET
Path	/orgs

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Snyk connection from the Connection dropdown.
3. In the Operation dropdown, select security.listOrgs.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Snyk API reference.

GET /orgs/{orgId}/projects

List projects

Detail	Value
Operation ID	security.listProjects
Method	GET
Path	/orgs/{orgId}/projects

Parameters

Name	Location	Type	Required
orgId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Snyk connection from the Connection dropdown.
3. In the Operation dropdown, select security.listProjects.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Snyk API reference.

GET /orgs/{orgId}/issues

List issues

Detail	Value
Operation ID	security.listIssues
Method	GET
Path	/orgs/{orgId}/issues

Parameters

Name	Location	Type	Required
orgId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Snyk connection from the Connection dropdown.
3. In the Operation dropdown, select security.listIssues.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Snyk API reference.

GET /orgs/{orgId}/targets

List targets

Detail	Value
Operation ID	security.listTargets
Method	GET
Path	/orgs/{orgId}/targets

Parameters

Name	Location	Type	Required
orgId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Snyk connection from the Connection dropdown.
3. In the Operation dropdown, select security.listTargets.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Snyk API reference.

GET /self

Get current user

Detail	Value
Operation ID	security.getSelf
Method	GET
Path	/self

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Snyk connection from the Connection dropdown.
3. In the Operation dropdown, select security.getSelf.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Snyk API reference.