> 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 can I build an Excel inventory of a Xiaohongshu creator’s notes?

> Page through a Xiaohongshu creator's notes with xiaohongshu.app_v2.get_user_posted_notes, write one spreadsheet row per note, and report saved pages, coverage and the stop reason.

To build an Excel inventory of a Xiaohongshu creator's notes, page through the creator's profile with `xiaohongshu.app_v2.get_user_posted_notes`, write one spreadsheet row per note, and retrieve details only for the notes you select. The finished sheet lists each note's link, the pages you saved and the reason each note was selected. The steps below use one example: reviewing the recipes a food creator posted last quarter.

## Fetch the first page from the profile

Pass the creator's verified `user_id`, or pass the creator's full profile share link as `share_text`. The example below uses a profile share link. Send the request to `POST https://api.beatapi.io/v1/social-data/call` with BeatAPI Bearer authentication, and replace `<confirmed_profile_share_link>` with the creator's real share link.

```json
{
  "action": "xiaohongshu.app_v2.get_user_posted_notes",
  "params": {"share_text": "<confirmed_profile_share_link>", "cursor": ""}
}
```

1. Check that the first batch of notes belongs to the target creator.
2. Save the request, the original response, the collection time and the request ID.
3. For the next page, pass the returned cursor as `cursor` and keep the same creator and the same other inputs. The input documentation gives `data.data.notes[-1].cursor` as an example continuation path.
4. Stop on an empty page, a repeated cursor, an error or your scope limit, and record which stop reason applied.

## Fill the sheet from actual results

Format the note ID column as text, then write one row per note. The columns below are working columns: keep each value as returned and mark each gap as pending.

| Column                                 | Use                                                             |
| -------------------------------------- | --------------------------------------------------------------- |
| Creator and note identity              | Deduplicate by confirmed note ID and retain the source position |
| Title, available wording and link      | Screen topics and record whether you read a card or details     |
| Actual publication time                | Filter to the quarter and flag unknown dates                    |
| Engagement values and observation time | Compare the same field over a comparable sample                 |
| Selection reason                       | For example, “includes preparation, worth reading in full”      |

Keep the original response next to the sheet. To deliver a CSV, export a UTF-8 CSV from your spreadsheet. The public input documentation for `xiaohongshu.app_v2.get_user_posted_notes` does not define every list field, so check your actual response before you map fields to columns. To get full material for selected notes, follow the [note ID and detail workflow](/faq/xiaohongshu-share-links).

For a third-quarter review, add a filter column with the values “In quarter,” “Date pending” and “Outside quarter.” When a note appears on two pages, keep one row and record both pages. After exporting, spot-check one row: the note ID must still be a complete string and must lead back to the correct note in the saved response.

In the delivery note, report the number of saved pages, the number of identifiable notes, the target quarter and the stop reason. When the list ends, write that you fetched every page the list returned for this run. Budget calls as list pages plus detail requests for selected notes; current prices are on the [pricing](https://beatapi.io/pricing) page.