Xiaohongshu Keyword Search

Search one Xiaohongshu keyword and return matching content identifiers with collection metadata.

Data collection

Developer

meme_today

Pricing

From $0.03 / 20 records

Last updated

2026-09-22

Overview

Researching how a topic appears in Xiaohongshu search often starts with finding a dependable set of matching content identifiers. This app turns one search keyword into a structured collection of matching items, keeping the keyword and collection context beside each identifier so the dataset remains understandable after it is exported or joined with other research material.

The result is useful as a discovery index: it shows which content items were associated with a brand, product, topic, or campaign at collection time. It is especially suited to building repeatable monitoring sets, comparing the content populations found for different terms, and preparing identifiers for later analysis without manually recording items from search pages.

Data notes

Each record represents one item associated with the submitted Xiaohongshu keyword. Content identifiers are de-duplicated within the returned dataset. Matched keyword, Source item, and Business ID preserve the collection context and may repeat across many records from the same search. Effective update time is returned without timezone information, so it should not be treated as an absolute cross-region timestamp without additional context. Account unique ID may be unavailable for some records.

The collection contains identifiers and collection metadata, not the full post body, title, media, engagement totals, comments, or a complete author profile. A No-data marker distinguishes task metadata that reports no matching content from ordinary matched records.

What a result looks like

Each row is one matched content item or a no-data marker associated with the search keyword.

Content ID	Matched keyword	Effective update time	Business ID	No-data marker
6a8ffa18000000000402a03c	蓝牙耳机	2026-08-27T16:56:13	蓝牙耳机	No
6a8ff9c900000000260068c2	蓝牙耳机	2026-08-27T16:56:13	蓝牙耳机	No

Account unique ID and Source item are also available when supplied with the record.

Use cases

For topic discovery, group rows by Matched keyword and count distinct Content ID values to compare the searchable content population associated with each term.
For monitoring, repeat a keyword collection and compare Content ID sets while using Effective update time as source-provided context for newly observed items.
For provenance checks, compare Matched keyword, Source item, and Business ID to confirm which search context produced each content item before combining datasets.
For data-quality review, filter on No-data marker and missing Account unique ID values to separate empty-search metadata from usable matched records.

Scope and boundaries

One keyword per task with an expected result count from 1 to 200; results are returned in complete batches of 20 and may be rounded up; coverage is limited to records available through Xiaohongshu keyword search.

Good for
When you need content identifiers returned by a Xiaohongshu keyword search for a brand, product, topic, or campaign.
When you need a structured list that connects each matched content item with its search keyword and collection metadata.

Do not use for
When you need full post text, media, engagement metrics, comments, or complete author profiles.
When you need an immediate single-record lookup rather than a background keyword collection task.

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

1If no matching records are returned, verify the keyword or try a shorter and broader search phrase.
2Keep completed records after a partial success; resubmit the same input after a failed or expired task.
3Retry later after rate limiting, temporary service unavailability, or a timeout.
4If authentication fails, verify the API Key configured for the execution environment.

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

Search keywordkeywordRequiredstring
A brand, product, topic, or phrase to search on Xiaohongshu. Each task accepts one keyword from 1 to 512 characters.
Example蓝牙耳机
Expected result countcrawl_countRequiredinteger
Expected number of search results, from 1 to 200. Results are returned in complete batches of 20, so the actual count may be rounded up.
Range1–200Example20

Output

Field structure of a single record, generated from the output.schema in manifest.json.

Content IDcontent_idstring
Unique identifier of the matched Xiaohongshu content item.
Example6a8ffa18000000000402a03c
Matched keywordkeywordstring
Search keyword associated with the collected content item.
Example蓝牙耳机
Effective update timeeffective_update_timestring
Timestamp associated with the collected record; the source does not specify a timezone.
Example2026-08-27T16:56:13
Account unique IDaccount_unique_idstring
Unique account identifier when available; this value may be missing.
Exampleaccount_example_001

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example

{
  "content_id": "6a8ffa18000000000402a03c",
  "keyword": "蓝牙耳机",
  "effective_update_time": "2026-08-27T16:56:13",
  "account_unique_id": "account_example_001",
  "biz_id": "蓝牙耳机",
  "source_item": "蓝牙耳机",
  "no_data": false
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config

{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-keyword-list",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

View my API Keys →

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (The prompt asks the AI to request your API key from you, so credentials never end up in chat history or shared configs.)

detail.access.mcp.composeHint

Pricing

20 returned records

Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 20 records; any partial unit is rounded up to 20 records.

$0.03/ 20 records

Per task submitted

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example

Parameters are validated against input.schema before submission

Search keywordkeyword*A brand, product, topic, or phrase to search on Xiaohongshu. Each task accepts one keyword from 1 to 512 characters.

Expected result countcrawl_count*Expected number of search results, from 1 to 200. Results are returned in complete batches of 20, so the actual count may be rounded up.

From $0.03 / 20 records