---
title: "Get Pipeline Learnings Route"
method: GET
path: "/api/pipeline/learnings"
tags: ["pipeline"]
---

# Get Pipeline Learnings Route

`GET /api/pipeline/learnings`

What the deal agent has learned from operator stage rulings.

Its OWN route, deliberately not a `scope` param on the prospecting endpoint:
that response shape is frozen for older installed mobile builds, and a new
param there would change what they receive.

`scope=all` merges every pipeline document and tags each item with its
`skill_name`, matching the prospecting endpoint so one UI component can
render either store.

## Query parameters

- `scope` string
- `user_id` string, nullable
- `org_id` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

- **2026-09-03** `cd6453ae5786` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/every/apis/every-api/changes/api/pipeline/learnings/get.md)

---

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