Rednote Note Detail API

Rednote Note Detail

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 contextReturn 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.

Parameters

How to Use

Provide a current token-bearing note URL, submit the asynchronous 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

Best Use Cases

• Enrich a known-note catalog: 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.

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; Note Detail 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.

Related APIs