> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/substack/notes-noteid-replies>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/substack/notes-noteid-replies.mdx>

---

# Substack Note Replies API

The reply branches under a note, each with its descendant comments.

`GET /v1/substack/notes/{noteId}/replies` returns the reply branches for a note. `data.root` is the note the replies belong to, and `data.replies[]` holds branches of `comment` plus `descendantComments[]`.

`data.noteId` names the note and `data.moreBranches` counts the reply branches not included in this response. `lookupStatus` is `found` or `not_found`. Each comment uses the note shape, so it carries `body`, `author`, engagement counts and attachments.

## Request

- **Endpoint:** `GET /v1/substack/notes/{noteId}/replies`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by note id
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/substack/notes/noteid/replies/get)
- **Platform page:** [/platforms/substack](https://www.socialfetch.dev/platforms/substack)

## FAQ

### How is a reply branch shaped?

Each branch has a `comment` and a `descendantComments` array. The branch's first comment is the reply; the descendants are the replies under it.

### What does moreBranches mean?

A response sometimes holds only some branches. `moreBranches` is the number left out, so you can tell a complete response from a partial one.

### Does this include reactions on replies?

Yes. Each comment carries `reactionCount`, `reactions`, `restackCount` and `replyCount` when available.

### How many credits does a replies lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.