---
title: 'GET /organizations/{organization_slug}/issues/'
description: 'List issues for an organization'
---

# GET /organizations/{organization_slug}/issues/

List issues for an organization

| Detail | Value |
|---|---|
| Operation ID | `devtools.listIssues` |
| Method | `GET` |
| Path | `/organizations/{organization_slug}/issues/` |
| Connector | [Sentry](./) |

## Parameters

| Name | Location | Type | Required |
|---|---|---|---|
| `organization_slug` | path | string | **Yes** |
| `query` | query | string | No |

## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your Sentry connection from the Connection dropdown.
3. In the Operation dropdown, select `devtools.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 Sentry API reference.