---
title: "runs.startFromLeads"
method: POST
path: "/v1/runs/start-from-leads"
tags: ["runs"]
---

# runs.startFromLeads

`POST /v1/runs/start-from-leads`

## Request

- Base URL: `https://api.selda.ai`
- URL: `https://api.selda.ai/v1/runs/start-from-leads`
- Auth: HTTP bearer

Start a campaign from leads already pushed in with selda_add_lead, selected by the source label you gave them. No discovery, Selda writes a message per lead from the analysis that came with it, and stops at the drafts.

Dispatched to `runs.startFromLeads` on `POST /mcp/run`. 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: `pipeline`
- A free sandbox key is refused: it runs the discovery and research engine: web search, crawls, model calls, per-lead credits
- MCP tools that wrap the same function: `selda_start_campaign_from_leads`
- Filled in from your API key, never sent by you: `orgId`

## Request body

- object
  - `projectId` string, required: A Convex document id in the `projects` table.
  - `source` string, required
  - `sourceDisplayLabel` string
  - `campaignId` string: A Convex document id in the `campaigns` table.
  - `campaignBrief` string

## 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)