Rednote Search Users
Public Rednote account search can surface identity, biography, profile status, and visible audience or content counts for people matching one text query. Normalized account records keep the source fields that are available and attach collected_at for traceable discovery and comparison.
Rednote Search Users API Features
- Single-query account discoverySubmit one non-empty query that maps to the provider keyword on its fixed first page, without source-page controls or additional filters.
- Normalized public identityThe Rednote Search Users API returns a stable account shape for available ID, username, display name, biography, public URL, profile imagery, website, verification, and privacy fields.
- Visible account snapshotKeep available follower, following, and post counts with collected_at so every returned value remains tied to its observation time.
Rednote Search Users API Parameters
| Parameters | Required | Description |
|---|---|---|
query | Required | Required non-empty string mapped to the provider keyword. This endpoint has no enum, results_limit, provider cursor, sort, or media filter fields. |
How to Use the Rednote Search Users API
Submit one account-search term to the Rednote Search Users API, follow the asynchronous task, and read its stored normalized account records.
- Choose one non-empty term representing the public account, creator name, brand, or topic you want to discover.
- Send query to /v1/rednote/search-users and save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
- Read data.results.items; if the stored-result response returns has_more, continue with its next_cursor.
curl -X POST "https://api.socq.ai/v1/rednote/search-users" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"photography"}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items; next_cursor paginates stored results onlyRednote Search Users API Use Cases
- Build a creator shortlist: Discover public accounts from a name or topical term, then review available identity and biography fields before selecting candidates.
- Enrich an account directory: Add normalized IDs, usernames, display names, profile text, imagery, URLs, websites, and account flags to a discovery list.
- Compare public account signals: Use available follower, following, and post counts as collected-at snapshots without treating them as private analytics or live totals.
Rednote Search Users API Pro Tips
- Submit only query; results_limit, cursor, page, sort, filter, media_type, and extra fields are rejected by this endpoint.
- Treat the provider call as one fixed first page. The shared task reader's next_cursor paginates stored SocQ rows, not additional Rednote source pages.
- Allow IDs, usernames, names, biography text, imagery, websites, account flags, and individual metrics to be null when the public response omits them.
- Store collected_at with visible counts, and budget a fixed 1.00 SocQ credits for every successful task regardless of the number of returned accounts.
Related APIs
Beyond the Rednote Search Users API, use these APIs when you need a different type of public Rednote data.