---
title: "signals.list"
method: POST
path: "/v1/signals/list"
tags: ["signals"]
---

# signals.list

`POST /v1/signals/list`

## Request

- Base URL: `https://api.selda.ai`
- URL: `https://api.selda.ai/v1/signals/list`
- Auth: HTTP bearer

The signals Selda has found for a workspace, newest first. Read-only: it changes nothing and spends nothing.

Dispatched to `signals.list` on `POST /mcp/mutate`. This route is a different URL for the same call: the request is answered by the same dispatcher, with the same authentication, the same scope check, the same organisation scoping and the same refusals.

- Scope: `write`
- A free sandbox key may call it
- MCP tools that wrap the same function: `selda_list_signals`
- Filled in from your API key, never sent by you: `orgId`
- A legacy entry. Its summary above says what that costs you.

## Request body

- object
  - `projectId` string, required: A Convex document id in the `projects` table.
  - `status` 'new' | 'used' | 'dismissed'
  - `limit` number

## Response `200`

The call succeeded.

- object
  - `value` unknown, required
  - `request_id` string, required: Echoed in the `X-Request-Id` header.

## Other responses

- `400`: Unknown route, or arguments the validator refused.
- `401`: Missing, expired or revoked key.
- `403`: The key lacks the scope, the plan entitlement, or is a sandbox key on a live-only function.
- `429`: Rate limited. Wait for the next minute window and retry.
- `500`: The function threw. The message says what, without leaking internals.

---

[API](https://skmtc.dev/selda/apis/selda-api.md) · [All operations](https://skmtc.dev/selda/apis/selda-api/llms.txt) · [OpenAPI document](https://skmtc.dev/selda/apis/selda-api/revisions/f0b115a94c0f?raw)