---
title: 'GET /orgs/{orgId}/issues'
description: 'List issues'
---

# GET /orgs/{orgId}/issues

List issues

| Detail | Value |
|---|---|
| Operation ID | `security.listIssues` |
| Method | `GET` |
| Path | `/orgs/{orgId}/issues` |
| Connector | [Snyk](./) |

## 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 <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Snyk API reference.