Rednote User Profile
Public Rednote profiles can expose an account identifier, Rednote handle, display name, biography, profile imagery, website, account flags, and visible follower, following, and post counts. A normalized record keeps those available identity fields and point-in-time signals together for account matching, selected-profile comparison, and repeat snapshot analysis.
Features
- Two lookup paths with explicit priorityResolve one profile from a supported Rednote URL or a public user_id. If both fields are supplied, the explicit user_id is used for the source lookup.
- Consistent public identity recordNormalize the available account ID, source URL, Rednote handle, display name, biography, avatar, cover image, website, verification flag, and privacy flag.
- Timestamped visible account signalsReturn available follower, following, and post counts beside collected_at so each result remains a point-in-time observation rather than a live total.
Parameters
| Parameters | Required | Description |
|---|---|---|
url | Required (at least one) | One of url or user_id is required. The parsed hostname must be xiaohongshu.com, xhslink.com, or a subdomain of either host. If user_id is also present, user_id takes priority. |
user_id | Required (at least one) | One of user_id or url is required. Use 1 to 256 ASCII letters, numbers, colons, underscores, or hyphens. This explicit identifier takes priority when url is also supplied. |
How to Use
Submit one supported account reference, track the asynchronous task, and read the normalized account from the stored result page.
- Prepare a current public user_id or a URL whose parsed hostname is xiaohongshu.com, xhslink.com, or a subdomain of either host.
- Submit user_id, url, or both to /v1/rednote/user-profile; when both are present, user_id takes priority. Save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
- Read the account in data.results.items. Use next_cursor only if the stored result reader reports has_more as true.
REDNOTE_USER_ID=''
# Paste a current public Rednote account identifier before running.
curl -X POST "https://api.socq.ai/v1/rednote/user-profile" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d "{\"user_id\":\"$REDNOTE_USER_ID\"}"
# Poll GET /v1/tasks/{task_id}
# Read data.results.items; follow next_cursor only while has_more is trueBest Use Cases
- Known-account enrichment: Turn an existing public Rednote account reference into a consistent identity record with available profile text, imagery, website, and account flags.
- Profile snapshot comparison: Compare selected accounts or repeated collections using stable result IDs, collected_at, and the follower, following, and post counts available at collection time.
Pro Tips
- Provide at least one input. When both url and user_id are present, the backend uses the explicit user_id and does not send the URL to the source lookup.
- Prefer user_id when you already have the public account identifier; it avoids depending on the structure of a shared or account URL.
- Validate user_id with ^[A-Za-z0-9:_-]{1,256}$ and require the parsed URL hostname to match xiaohongshu.com, xhslink.com, or a subdomain before submission.
- Do not add results_limit or a source cursor. This endpoint makes one detail request, while next_cursor belongs only to the SocQ stored-result reader.
- Treat biography, profile imagery, website, flags, and every metric as optional. Preserve nulls instead of converting missing fields to empty strings or zero.
- A prior Rednote account result can supply its canonical id for user_id. Keep that identifier distinct from the returned username, which represents the available Rednote handle.
Related APIs
Use these APIs when you need a different type of public Rednote data.