Rednote Home Recommendations
A home recommendation request retrieves one public Rednote feed page without requiring a profile, note URL, or search phrase. Each available item is projected into a standard post record with source identity, text, author, media, visible engagement, publication time, and collection time.
Features
- Seedless home-feed requestSubmit an empty body or the verified homefeed_recommend category to request one current recommendation page without inventing a user or query input.
- Bounded page sizeRequest an integer from 1 through 40; omission uses 20 while the returned page may contain fewer public items.
- Provider-independent post shapeRead available note identity, text, author, media, timestamps, and visible metrics through the shared post schema instead of provider field names.
- Durable asynchronous resultsSubmit once, follow the task status, and page through records stored by SocQ after the provider's single response has been normalized.
Parameters
| Parameters | Required | Description |
|---|---|---|
category | Optional | Optional non-empty string. When omitted, the provider mapping injects homefeed_recommend. That is the only backend-defined category documented here; other strings are not presented as verified categories. |
media_type | Optional | Optional enum: all, image, or video. The current mapping sets the provider image flag only for image; all and video both map to false, so video does not guarantee an exclusive video-only response. |
results_limit | Optional | Optional positive integer from 1 through 40. It defaults to 20, sets the requested provider page size, and caps stored rows when explicitly supplied. |
How to Use
Choose only verified optional values, submit the asynchronous request, and read the stored standard results.
- Start with the backend defaults, or set category, media_type, and results_limit explicitly.
- POST the JSON body to /v1/rednote/home-recommendations and save data.task_id from the submission response.
- Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
- Read data.results.items; follow next_cursor only when has_more refers to additional SocQ-stored records.
curl -X POST "https://api.socq.ai/v1/rednote/home-recommendations" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"category":"homefeed_recommend","media_type":"all","results_limit":20}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items; next_cursor paginates stored results onlyBest Use Cases
- Recommendation-page snapshots: Capture a bounded public home-feed page with collected_at so every item stays tied to one observation.
- Editorial discovery queues: Feed normalized post text, authors, and media references into a human review or classification workflow.
- Visible-content audits: Compare the available media mix and public engagement fields across separately submitted recommendation tasks.
Pro Tips
- Use {} when you want all provider defaults; no field is required by the public request validator.
- Keep category at homefeed_recommend unless you have independently validated another provider category; the runtime accepts a non-empty string but does not publish a category enum.
- Treat media_type=video cautiously because it currently maps to the same provider flag as all; only image changes that flag.
- Choose results_limit between 1 and 40, and do not assume the provider will return exactly the requested number of public items.
- Do not send a provider cursor: the upstream executor makes one request and reads items, notes, or feeds from that single response.
- Use next_cursor only to continue through SocQ-stored results after success; it does not fetch another Rednote page.
- Budget a fixed 1.00 SocQ credit per task; the charge does not scale with the selected limit or returned item count.
Related APIs
Use these APIs when you need a different type of public Rednote data.