# Xiaohongshu Profile Posts API (https://www.socialcrawl.dev/platforms/xiaohongshu/profile-posts)

> Returns a Xiaohongshu creator's notes, newest first. Each row has a title, a short summary (post.ext.text_truncated is true) and engagement counts. Pinned notes set post.flags.pinned. Pass the returned cursor to read further. Xiaohongshu does not publish view counts, so post.engagement.views is null.

TL;DR: `GET /v1/xiaohongshu/profile/posts` costs 5 credits per row RETURNED. The call holds `limit x 5` up front and settles down to the rows actually delivered. With `max_pages`, `max_items` or `max_credits`, each page walked is billed at this price (a cached page is free), and `max_credits` caps the total. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | no | Xiaohongshu profile URL. |
| `id` | no | User id, the author_user_id on a note. Not the RedNote id. |
| `limit` | no | Rows to return, 1 to 20. Default 10. Each row costs 5 credits and you are charged only for rows returned. |
| `cursor` | no | Continuation token from a previous response's pagination block. Omit for the first page. |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/xiaohongshu/profile/posts" \
  --data-urlencode "url=https://www.xiaohongshu.com/user/profile/6a59f257000000000f03b000" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### What does the Xiaohongshu Profile Posts API return?

Returns a Xiaohongshu creator's notes, newest first, with title, summary, engagement and cover image. The response uses the same JSON envelope as every SocialCrawl endpoint, with the data, credits_used and request_id fields.

### When should I use the Xiaohongshu Profile Posts endpoint?

Use it to read what a creator has published. Summaries are truncated, so open a note for the full text.

### How much does the Xiaohongshu Profile Posts API cost?

The price depends on the request, from 5 to 100 credits per call. Every new account gets 100 free credits. Credits for failed or empty calls are refunded automatically, and there is no subscription.

### What parameters does the Xiaohongshu Profile Posts API need?

Identify the target with one of url, id. It also accepts 9 optional parameters, all listed on this page.

### How do I call the Xiaohongshu Profile Posts API?

Send a GET request to https://www.socialcrawl.dev/v1/xiaohongshu/profile/posts?url=https%3A%2F%2Fwww.xiaohongshu.com%2Fuser%2Fprofile%2F6a59f257000000000f03b000 with your API key in the x-api-key header. An Authorization: Bearer header works too.

See the full Xiaohongshu API: https://www.socialcrawl.dev/platforms/xiaohongshu

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- What does the SocialCrawl Xiaohongshu Profile Posts API return?
- How do I get Xiaohongshu Profile Posts data with the SocialCrawl API?