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.
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 pageRun page 1 of the selected search once per task, producing a defined snapshot rather than claiming an exhaustive multi-page source crawl.
Parameters
| Parameters | Required | Description |
|---|---|---|
query | Required | Required non-empty text used to search public Rednote notes; the Playground leaves it blank until you provide your own term. |
sort_by | Optional | Optional result ordering: general, latest, or most_liked. The Playground starts with general. |
media_type | Optional | Optional note-format filter: all, image, or video. The Playground starts with all. |
published_within | Optional | Optional publication-window filter: all, day, week, or six_months. The Playground starts with all. |
How to Use
Submit a Rednote search query and optional filters, track the asynchronous task, then read the stored note records with SocQ cursor pagination.
- Prepare a non-empty query and choose only supported sort_by, media_type, and published_within values.
- POST the payload to /v1/rednote/search-notes and save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
- 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 trueBest Use Cases
- Keyword result cataloging: Use note IDs, public URLs, text, author references, and collected_at 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.
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.
Related APIs
Use these APIs when you need a different type of public Rednote data.