---
title: "Change a lead status"
method: POST
path: "/leads/{id}/status"
tags: ["Leads"]
---

# Change a lead status

`POST /leads/{id}/status`

## Request

- Base URL: `https://joinways.app/api/v1`
- URL: `https://joinways.app/api/v1/leads/{id}/status`
- Auth: one of:
  - HTTP bearer
  - OAuth 2 (authorization code, authorization URL `https://joinways.app/oauth/authorize`, token URL `https://joinways.app/api/oauth/token`, scopes: `mcp.write`)

Same rules as the Inbox. `validated` needs an event: the lead's own, or the event of its sibling at the same venue (then linked); otherwise `409 validation_requires_event` (convert the lead instead). Leaving `needs_info` clears the information request, except for a rejection, which keeps it (the venue did answer). A rejection may carry `rejection_reason`; any other status clears it. **Role permission:** `leads.manage`.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `status` 'pending' | 'validated' | 'rejected' | 'needs_info', required: `pending` = to process, `validated` = accepted (it has an event), `rejected` = declined, `needs_info` = waiting for information from the client.
  - `rejection_reason` 'date_unavailable' | 'capacity' | 'budget' | 'not_a_fit' | 'other': Why the venue declined the request (optional). Only set on a `rejected` lead; cleared as soon as the status changes.

## Response `200`

The new status.

- object
  - `id` string, uuid
  - `status` 'pending' | 'validated' | 'rejected' | 'needs_info': `pending` = to process, `validated` = accepted (it has an event), `rejected` = declined, `needs_info` = waiting for information from the client.
  - `client_name` string, nullable
  - `company` string, nullable
  - `event_id` string, uuid, nullable
  - `rejection_reason` 'date_unavailable' | 'capacity' | 'budget' | 'not_a_fit' | 'other': Why the venue declined the request (optional). Only set on a `rejected` lead; cleared as soon as the status changes.

## Other responses

- `400`: Validation failed (`invalid_request`). For a body that fails the schema, `details` holds `formErrors` and `fieldErrors`.
- `401`: Missing, invalid, expired or revoked bearer token (`unauthorized`).
- `403`: `forbidden`: the token lacks the scope, its owner's role lacks the permission named by the operation, or the workspace has neither the Pro plan nor a trial (`details.reason` `plan_not_eligible`).
- `404`: Not found in this workspace, or the id of the path is not a UUID (`not_found`).
- `409`: The state of the record refuses the operation (`conflict`). `details.reason` is a stable code.
- `429`: Too many requests (`rate_limited`). `details.reason`: `per-ip`, `per-account-minute`, `per-account-day`, or `email_rate_limited` (email budget). Always carries `Retry-After`: wait that many seconds.

---

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