---
title: "List Meeting Decisions"
method: GET
path: "/meetings/{meeting_id}/decisions"
tags: ["meetings"]
---

# List Meeting Decisions

`GET /meetings/{meeting_id}/decisions`

## Request

- Base URL: `https://api.3gppscout.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.3gppscout.com/meetings/{meeting_id}/decisions`
- Auth: none declared

Decisions recorded at one 3GPP meeting (for example R1-126): agreements, working assumptions,
conclusions, FFS items, and CR, LS, and way-forward outcomes, each with a verbatim quote and its source.
CR outcomes have decision_type approved_cr; way-forward and LS outcomes are agreement or endorsed. A
decision_type that is not one of these is mapped to its nearest type or ignored, and `warnings` says which.

Decisions come only from decision sources: chair notes, meeting and session reports, feature-lead
summaries, and the register status. They are never inferred from proposals. A summary record counts only
when the meeting's chair notes or reports record the same text; the rest are left out unless
source_kind=summary is passed, and then carry `confirmed_by_meeting_record: false`. Each decision names the
source TDoc and anchor, the TDoc it was recorded under (usually a feature-lead summary), the TDocs it
references, and the proposals it adopts. The same outcome recorded in several sources is returned once,
from chair notes first, with the others in `also_recorded_in`. `coverage` lists the meeting's decision
sources and whether each has been processed, so an empty list is a real "nothing found".

With `q`, decisions are matched to the topic by meaning (embedding similarity and a reranker, so
"timing advance" finds "UL time/frequency pre-compensation") and by exact identifiers, and returned
most relevant first, each with `topic_relevance`. Only relevant decisions are returned, unless
`agenda_item` is also given: then every decision under the item is returned, ranked by the topic.
When nothing is relevant, `decisions` is empty and `message` says so. A page stops early rather than
exceed about 60,000 characters; follow `next_cursor`.

## Path parameters

- `meeting_id` string, required

## Query parameters

- `agenda_item` string, nullable: Comma-separated agenda items; '10.7' also matches 10.7.1.
- `decision_type` string[], nullable: Decision types to return. CR outcomes are approved_cr; way-forward and LS outcomes are agreement or endorsed. Default: every type except noted.
- `q` string, nullable: Topic, matched by meaning and by exact identifiers, e.g. 'NTN timing advance' or 'ta-CommonDrift'.
- `source_kind` string, nullable: Comma-separated: chair_notes, report, summary, register.
- `limit` integer
- `cursor` string, nullable: next_cursor from a previous response.

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/3gppscout/apis/3gpp-scout-api.md) · [All operations](https://skmtc.dev/3gppscout/apis/3gpp-scout-api/llms.txt) · [OpenAPI document](https://skmtc.dev/3gppscout/apis/3gpp-scout-api/revisions/60bd6896e5b9?raw)