---
title: "Find Topics To Follow"
method: POST
path: "/follows/resolve"
tags: ["follow"]
---

# Find Topics To Follow

`POST /follows/resolve`

## 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/follows/resolve`
- Auth: none declared

Preview what following something would cover, before following it.

Turns free text into catalog targets (topics, work items, specs, companies, meetings, groups), each with a
label, a one-line reason, a confidence and an `included` flag (low-confidence targets come back unchecked).
Also returns a coverage note, how many updates it would have matched in the last 90 days with examples,
and `confirmation.text` to show the user. When the text names a subject, `phrase` says that the follow is
also matched by meaning (`phrase.text` to show), which works even when no catalog target fits. Follow with
POST /follows (follow_topic) using the targets the user kept. Following does not count against API
request allowances.

## Request body

- ResolveRequest
  - `query` string, required: What to follow in plain words: a topic ('NTN timing advance'), a company ('Ericsson'), a spec ('TS 38.331'), a meeting ('RAN1 #127'), or a mix ('Qualcomm AI/ML in RAN1').

## 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)