rednote/
search-notes

The Rednote Search Notes API searches public Rednote notes by text query with optional sort, media, and time filters, returning normalized content, authors, media, timestamps, and visible engagement.

Rednote Search Notes API

Keyword note search
Sort and media filters
One-page public snapshot
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 Search Notes

Rednote Search Notes are public posts matched to a keyword, with note identity, text, author context, media, publication time, and visible engagement. These records support topic research, format comparison, source review, and point-in-time search-result analysis.

Rednote Search Notes API Features

  • Keyword search with three filter dimensionsAccept one text query plus supported ordering, media-type, and publication-window selections to define a focused public note search.
  • Normalized note identity and contentReturn note IDs, public URLs, text, resource type, publication time, and collection time in the shared PostItem structure.
  • Author, media, and visible engagement contextPreserve available public author fields, image or video references, hashtags, mentions, and visible like, comment, share, and view counts.
  • Bounded source search pageEach Rednote Search Notes API task runs page 1 of the selected search once, producing a defined snapshot rather than claiming an exhaustive multi-page source crawl.

Rednote Search Notes API Parameters

ParametersRequiredDescription
queryRequiredRequired non-empty text used to search public Rednote notes; the Playground leaves it blank until you provide your own term.
sort_byOptionalOptional result ordering: general, latest, or most_liked. The Playground starts with general.
media_typeOptionalOptional note-format filter: all, image, or video. The Playground starts with all.
published_withinOptionalOptional publication-window filter: all, day, week, or six_months. The Playground starts with all.

How to Use the Rednote Search Notes API

Submit a search query and optional filters to the Rednote Search Notes API, track the asynchronous task, then read the stored note records with SocQ cursor pagination.

  1. Prepare a non-empty query and choose only supported sort_by, media_type, and published_within values.
  2. POST the payload to /v1/rednote/search-notes and save the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
  4. Read data.results.items and follow next_cursor while has_more is true; this paginates stored results, not additional Rednote search pages.
curl -X POST "https://api.socq.ai/v1/rednote/search-notes" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"query\":\"$REDNOTE_SEARCH_QUERY\",\"sort_by\":\"general\",\"media_type\":\"all\",\"published_within\":\"all\"}"

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Rednote Search Notes API Use Cases

  • Keyword result cataloging: Use the note IDs, public URLs, text, author references, and collected_at from the Rednote Search Notes API to build a traceable snapshot for a defined query.
  • Image and video result comparison: Run separate media_type selections and compare returned media references, note text, and visible engagement across the resulting snapshots.
  • Recency-focused topic review: Combine latest ordering or a publication window with published_at and collected_at to review recently surfaced notes for one topic.
  • Author-context analysis: Associate matched note text and media with available author identity fields to examine which public accounts appear in a query snapshot.

Rednote Search Notes API Pro Tips

  • Trim the query and confirm it is non-empty before submission so required-field validation does not reject the task.
  • Use only the documented enum values; choose general, all, and all when you want the broadest explicitly configured search.
  • Treat each task as one source search page, and run separate tasks for different filter combinations instead of assuming the snapshot covers later source pages.
  • Follow next_cursor until has_more is false when the stored snapshot spans multiple SocQ result pages; this cursor never requests another Rednote source page.
  • Use note ID and URL when reconciling separate query runs because ordering and visible metrics can differ between collection times.
  • Handle text, author fields, media, publication time, hashtags, mentions, and individual metrics as nullable, and escape public text before rendering it.

Explore other platforms

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

Rednote Search Notes API — FAQ

Rednote Search Notes API finds public Rednote notes from one text query with optional ordering, media-type, and publication-window filters, returning normalized note identity, text, author context, media, timestamps, and visible engagement fields.

query is required. sort_by accepts general, latest, or most_liked; media_type accepts all, image, or video; published_within accepts all, day, week, or six_months.

The default example uses query 旅行攻略 with sort_by general and media_type all, while published_within is omitted. The endpoint does not accept results_limit, a page number, or a source cursor.

Each PostItem can contain note ID, URL, text, author details, media, publication and collection timestamps, hashtags, mentions, and visible like, comment, share, and view counts. Optional source values remain null when unavailable.

No. Each task requests source page 1 once; next_cursor only reads the next page of results already stored by SocQ, with task-result limits from 1 through 500 and 50 by default.

Each task uses a fixed 1 SocQ credit. The number of notes stored or returned does not change that fixed task charge.