rednote/
user-profile

The Rednote User Profile API retrieves one public Rednote profile by supported account URL or user_id, returning normalized identity, profile imagery, account flags, visible counts, and collection time.

Rednote User Profile API

URL or user_id
One normalized account
Fixed 1-credit task
1 credit / request
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

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.

Rednote User Profile API 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 signalsThe Rednote User Profile API returns available follower, following, and post counts beside collected_at so each result remains a point-in-time observation rather than a live total.

Rednote User Profile API Parameters

ParametersRequiredDescription
urlRequired (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_idRequired (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 the Rednote User Profile API

Submit one supported account reference to the Rednote User Profile API, track the asynchronous task, and read the normalized account from the stored result page.

  1. Prepare a current public user_id or a URL whose parsed hostname is xiaohongshu.com, xhslink.com, or a subdomain of either host.
  2. Submit user_id, url, or both to /v1/rednote/user-profile; when both are present, user_id takes priority. Save the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
  4. 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 true

Rednote User Profile API Use Cases

  • Known-account enrichment: Use the Rednote User Profile API to turn an existing public 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.

Rednote User Profile API 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. The Rednote User Profile API 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.

Explore other platforms

Combine Rednote data with public data from other supported social platforms.

Rednote User Profile API — FAQ

Rednote User Profile API retrieves at most one public Rednote profile from a supported account URL or user_id and returns a normalized account record.

Use user_id when it is known. You may submit both fields, but the explicit user_id takes priority and the URL is not forwarded to the source lookup.

A URL must parse to xiaohongshu.com, xhslink.com, or a subdomain. user_id must contain 1 to 256 ASCII letters, numbers, colons, underscores, or hyphens.

A result can include ID, source URL, Rednote handle, display name, biography, avatar, cover image, website, verification and privacy flags, follower, following, and post counts, and collection time. Individual fields may be null.

No. user_id is an accepted lookup identifier and the canonical result has its own id. username contains the Rednote handle when the source supplies one, so callers should not substitute it for user_id without verifying the source value.

No. One task makes one profile-detail request and can store at most one account. The common task result response still includes items, next_cursor, and has_more for reading records stored by SocQ.

Each successful Rednote User Profile task costs a fixed 1.00 SocQ credit. The request is not priced by field count or stored result count.