> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How do Lemon8 share links resolve, and is item_id enough to fetch comments?

> Resolve Lemon8 post share links via lemon8.app.get_item_id with share_text, then call fetch_post_detail to obtain group_id, item_id, and media_id required by fetch_post_comment_list.

Pass a copied Lemon8 post link as `share_text` to `lemon8.app.get_item_id` to resolve the post's `item_id`. `item_id` alone cannot fetch comments: `fetch_post_comment_list` requires `group_id`, `item_id`, and `media_id`, and `fetch_post_detail` returns all three identifiers for the post.

## Where does copied share text go?

`lemon8.app.get_item_id` accepts a copied long or short post link in `share_text`. For an account share link, call `get_user_id` instead of passing a user ID as a post ID. If you already have `item_id`, call `fetch_post_detail` directly and skip the paid link-resolution step.

## Why do comments require three IDs?

`fetch_post_comment_list` requires `group_id`, `item_id`, and `media_id`. Either `lemon8.app.get_item_id` or `fetch_post_detail` supplies `item_id`, whereas only `fetch_post_detail` supplies `group_id` and `media_id`. All three fields are distinct identifiers: never copy `item_id` into `group_id` or `media_id`, and never substitute a username. Save the raw `fetch_post_detail` response first, then extract all three values for the target post directly from that response. BeatAPI passes through sanitized `data` responses without normalizing every Lemon8 action to `data.item`.

## Can I reuse follower pagination for comments?

No. Lemon8 actions use distinct continuation parameters:

| Action                       | Continuation field |
| ---------------------------- | ------------------ |
| Comments                     | string `offset`    |
| Follower and following lists | `cursor`           |
| Search                       | `max_cursor`       |
| Topic posts                  | `max_behot_time`   |

Because the schema default for comment `offset` is `"0"` while the parameter note describes an empty first value, send the explicit default `"0"` on the first `fetch_post_comment_list` request. On subsequent pages, pass the `offset` returned by the previous response unchanged instead of incrementing `offset` manually, while keeping the post identifiers and action fixed. Stop when `offset` repeats or is missing, or when a request returns an error; interrupted pagination does not mean every comment was collected.

For example, if a teammate shares a packing video and you want to check whether viewers asked about suitcase size, resolve `share_text` with `lemon8.app.get_item_id`, verify in `fetch_post_detail` that the post matches the video, and pass `group_id`, `item_id`, and `media_id` from `fetch_post_detail` to `fetch_post_comment_list`. Archive the share URL, `item_id`, and selected comment excerpts together.

[Search filters](/faq/lemon8-search-filters) · [Search and archive](/guides/lemon8-search-archive)