---
title: "Leads behind one 'Motivos de Perda' row (paged drill-down)"
method: GET
path: "/api/leads/reports/lost-reason-leads"
tags: ["Leads - Admin"]
---

# Leads behind one 'Motivos de Perda' row (paged drill-down)

`GET /api/leads/reports/lost-reason-leads`

Page through the leads of one card row, newest loss first.

`start_date`/`end_date` are REQUIRED and are the `window` the report echoed:
the dialog must show the same population the card counted, and re-deriving
the window from `period` at click time would drift by the page's dwell time.

A card row can cover several stored values (the FE merges by resolved label),
hence `reason` is repeatable; `include_no_reason` selects the NULL/blank
"Sem motivo indicado" bucket, which `IN (...)` can never match.

## Query parameters

- `reason` string[]
- `include_no_reason` boolean
- `start_date` string
- `end_date` string
- `team_id` integer[]
- `include_no_funnel` boolean — Also match leads with no (or an orphaned) attribution funnel
- `offset` integer
- `limit` integer

## Headers

- `x-api-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/multigest/apis/multigest-protected-api.md) · [All operations](https://skmtc.dev/multigest/apis/multigest-protected-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/multigest/multigest-protected-api/revisions/4b44eb76b3ee/schema)