---
title: "Get Finding"
method: GET
path: "/api/findings/{finding_id}"
tags: ["agents"]
---

# Get Finding

`GET /api/findings/{finding_id}`

## Request

- Base URL: `https://api.parlel.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.parlel.com/api/findings/{finding_id}`
- Auth: none declared

One finding the viewer may see, in the same shape the feed card renders.

Digest Apply via Parlel links land on ``/feed?apply=<id>``. That finding is
often not on the first page of ``/feed`` (newest-first, and the email can
be days old), so the feed fetches this row and pins it at the top instead
of hoping the reader scrolls far enough to recognise it.

## Path parameters

- `finding_id` string, required

## Headers

- `authorization` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

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