rednote/
note-detail

The Rednote Note Detail API retrieves one public Rednote note from a token-bearing xiaohongshu.com or xhslink.com URL, returning normalized text, author, media, timestamps, and visible engagement.

Rednote Note Detail API

Token-bearing note URL
Single-note detail
Normalized post record
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 Note Detail

Rednote notes are public content objects that pair text and media with author identity, topic references, publication time, and visible engagement. These fields support known-link enrichment, content review, and point-in-time comparison of selected notes.

Rednote Note Detail API Features

  • Token-qualified note lookupResolve one known public note URL only when its accepted host, note-detail path, and non-empty xsec_token identify a complete source lookup.
  • Note and author contextThe Rednote Note Detail API returns normalized note identity, source URL, text, timestamps, and available author ID, username, display name, profile URL, avatar, and account flags.
  • Media and engagement snapshotKeep available media references, previews, dimensions, duration, topic references, and visible like, comment, share, and view counts with collection time.

Rednote Note Detail API Parameters

ParametersRequiredDescription
urlRequiredRequired non-empty URL on xiaohongshu.com, xhslink.com, or a subdomain. Its path must include /explore/{note_id} or /discovery/item/{note_id}, and its query must contain a non-empty xsec_token.

How to Use the Rednote Note Detail API

Provide a current token-bearing note URL, submit the asynchronous Rednote Note Detail API request, and read the single normalized post record after completion.

  1. Copy a current public note URL whose accepted host, note-detail path, and query string include a non-empty xsec_token.
  2. POST the url to /v1/rednote/note-detail and save data.task_id from the submission response.
  3. Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
  4. Read data.results.items after success. The source lookup is a single detail request; next_cursor only pages SocQ-stored records.
REDNOTE_NOTE_URL=''
# Paste a current public note URL with xsec_token between the quotes

curl -X POST "https://api.socq.ai/v1/rednote/note-detail" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"url\":\"$REDNOTE_NOTE_URL\"}"

# Poll GET /v1/tasks/{task_id}
# Read the normalized post from data.results.items

Rednote Note Detail API Use Cases

  • Enrich a known-note catalog: Use the Rednote Note Detail API to turn a qualified note URL into normalized identity, text, author, publication time, and source fields for an existing content index.
  • Review selected note content: Use text, author context, media references, and topic fields to inspect a defined set of individual public notes.
  • Compare engagement observations: Pair visible like, comment, share, and view counts with collected_at across separately submitted lookups for point-in-time comparison.

Rednote Note Detail API Pro Tips

  • Use the complete note URL, including its host, /explore/ or /discovery/item/ path, and xsec_token query parameter; a bare note ID cannot pass validation.
  • Keep xsec_token inside the URL query because the request accepts only url and rejects a separate token field.
  • When reusing a URL from another SocQ Rednote note result, confirm that xsec_token is still present; the Rednote Note Detail API cannot reconstruct a missing token.
  • Submit one URL per task because this detail endpoint has no batch field, results_limit, or source cursor input.
  • Treat next_cursor as stored-result pagination only; the source performs one detail lookup and normally produces at most one record.
  • Store author, media, topic, timestamp, and engagement fields defensively, and pair visible counters with collected_at because optional public values can be absent.

Explore other platforms

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

Rednote Note Detail API — FAQ

Rednote Note Detail API retrieves one public Rednote note from a token-bearing URL on an accepted host, returning normalized note identity, text, author, media, topic references, timestamps, and visible engagement fields.

Use a non-empty URL on xiaohongshu.com, xhslink.com, or a subdomain. Its path must contain /explore/{note_id} or /discovery/item/{note_id}, and its query must include a non-empty xsec_token.

No. The public request schema accepts only url; SocQ extracts note_id and xsec_token from that URL.

Submit a current public note URL that already includes xsec_token. A URL returned by another SocQ Rednote note endpoint is reusable only when that query parameter remains present; Note Detail does not create a missing token.

The normalized post record can include note identity, URL, text, publication and collection times, author details, media, hashtags, mentions, and visible like, comment, share, and view counts. Optional public fields can be null.

No. The source performs one detail lookup and saves at most one record. The shared task reader still exposes limit, next_cursor, and has_more for SocQ-stored records.

The endpoint is configured at a fixed 1.00 SocQ credit per task. The estimate does not scale with the returned record count.