---
title: "Undo a replied-outside mark (back to awaiting reply)"
method: POST
path: "/leads/{conversationId}/unresolve"
tags: ["leads"]
---

# Undo a replied-outside mark (back to awaiting reply)

`POST /leads/{conversationId}/unresolve`

## Request

- Base URL: `https://portal.fractionalteams.com/api/v1`
- URL: `https://portal.fractionalteams.com/api/v1/leads/{conversationId}/unresolve`
- Auth: HTTP bearer

Idempotent (see markLeadRepliedOutside). Same permission rules.

## Path parameters

- `conversationId` string, required

## Request body

- LeadMarkBody
  - `contact_name` string: The lead's name, for the audit trail

## Response `200`

Updated status

- LeadWriteResult
  - `ok` true, required
  - `conversation_id` string, required
  - `status` 'awaiting' | 'replied_outside', required
  - `unchanged` boolean: Present and true when the lead was already in the requested status (nothing written, nobody notified)

## Other responses

- `400`: Invalid conversation id
- `401`: Missing or invalid API key (a malformed ftpk_ key never falls back to the demo workspace).
- `403`: This key cannot mark leads
- `404`: Conversation not found in any published report visible to this key
- `429`: Rate limit exceeded (120 requests per minute per key). Honour Retry-After / RateLimit-Reset.

---

[API](https://skmtc.dev/fractionalteams/apis/fractional-teams-portal-api.md) · [All operations](https://skmtc.dev/fractionalteams/apis/fractional-teams-portal-api/llms.txt) · [OpenAPI document](https://skmtc.dev/fractionalteams/apis/fractional-teams-portal-api/revisions/9f81154af4dc?raw)