---
title: "Observation history and change events for one lead"
method: GET
path: "/api/v1/leads/{id}/timeline"
---

# Observation history and change events for one lead

`GET /api/v1/leads/{id}/timeline`

## Request

- Base URL: `https://lyreleads.com`
- URL: `https://lyreleads.com/api/v1/leads/{id}/timeline`
- Auth: HTTP bearer

What we have seen about this business over time and what changed between enriched runs: review-count surges, rating moves, technology added or removed, hiring flips. Events are only emitted between two successful enriched runs, never from a degraded one, and a removal needs two consecutive misses before it counts. This is how you feed change signals into your own system.

## Path parameters

- `id` integer, required

## Response `200`

observations[] and events[]

## Other responses

- `404`: Not found, or not yours

---

[API](https://skmtc.dev/lyreleads/apis/lyre-leads-api.md) · [All operations](https://skmtc.dev/lyreleads/apis/lyre-leads-api/llms.txt) · [OpenAPI document](https://skmtc.dev/lyreleads/apis/lyre-leads-api/revisions/1c7c73cc355f?raw)