Xiaohongshu Trending API

POST

API health

24h health
Normal
24h average time
—
Last checked
September 26, 2026 at 18:05 (UTC)
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Health APINormal
How health is measured
  • Health = the share of calls that returned data, in percent. Empty results, failures and unknown outcomes do not count as returning data.
  • Levels: 90% and above is healthy, 70% and above is available, 40% and above is limited; anything lower is mostly down.
  • A period (the last 24 hours, one hour or one day) gets a score only once it has at least 50 calls. Periods with fewer calls show as normal: a few failures among a handful of calls do not mean the API is down.
  • Calls include real customer calls and our own daily probe calls. Request errors (wrong parameters, no balance) are excluded.
  • Average time counts only calls that completed normally: response time for sync calls, acceptance to completion for async ones.
By period
Time (UTC)StatusHealthAverage time
2026-09-26 18:00 - 18:59Normal——
2026-09-26 17:00 - 17:59Normal——
2026-09-26 16:00 - 16:59Normal——
2026-09-26 15:00 - 15:59Normal——
2026-09-26 14:00 - 14:59Normal——
2026-09-26 13:00 - 13:59Normal——
2026-09-26 12:00 - 12:59Normal——
2026-09-26 11:00 - 11:59Normal——
2026-09-26 10:00 - 10:59Normal——
2026-09-26 09:00 - 09:59Normal——
2026-09-26 08:00 - 08:59Normal——
2026-09-26 07:00 - 07:59Normal——
2026-09-26 06:00 - 06:59Normal——
2026-09-26 05:00 - 05:59Normal——
2026-09-26 04:00 - 04:59Normal——
2026-09-26 03:00 - 03:59Normal——
2026-09-26 02:00 - 02:59Normal——
2026-09-26 01:00 - 01:59Normal——
2026-09-26 00:00 - 00:59Normal——
2026-09-25 23:00 - 23:59Normal——
2026-09-25 22:00 - 22:59Normal——
2026-09-25 21:00 - 21:59Normal——
2026-09-25 20:00 - 20:59Normal——
2026-09-25 19:00 - 19:59Normal——
2026-09-26Normal——
2026-09-25Normal——
2026-09-24Normal——
2026-09-23Normal——
2026-09-22Normal——
2026-09-21Normal——
2026-09-20Normal——
2026-09-19Normal——
2026-09-18Normal——
2026-09-17Normal——
2026-09-16Normal——
2026-09-15Normal——
2026-09-14Normal——
2026-09-13Normal——
2026-09-12Normal——
2026-09-11Normal——
2026-09-10Normal——
2026-09-09Normal——
2026-09-08Normal——
2026-09-07Normal——
2026-09-06Normal——
2026-09-05Normal——
2026-09-04Normal——
2026-09-03Normal——
2026-09-02Normal——
2026-09-01Normal——
2026-08-31Normal——
2026-08-30Normal——
2026-08-29Normal——
2026-08-28Normal——

Retrieve current trends from Xiaohongshu. Accepts these parameters: date_range, content_type, and sort. Returns these fields: author_name, image_url, is_video, and title.

Price $5.56 per 1,000 requests ($0.005556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

Request parameters

NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesxiaohongshuPlatform identifier, fixed value.
actionbodystringYestrendingCapability identifier, fixed value.
content_typebody.paramsenumNo-Filters returned notes by content type, such as image/text or video. Use the allowed values listed for the current action.Allowed valuesall_typesimage_notes_onlylive_notes_onlyvideo_notes_only
date_rangebody.paramsenumNo-Filters published notes by relative time window in the trending action. Allowed values are any_time, last_24_hours, last_7_days, and last_6_months. Applies to note creation dates, not comment timestamps.Allowed valuesany_timelast_24_hourslast_6_monthslast_7_days
sortbody.paramsenumNo-Sets the sorting order for notes or comments. Options include relevance, newest, popular, most_liked, most_commented, and most_collected. Supported values vary by action; search sorting values cannot be applied to comment endpoints.Allowed valuesmost_collectedmost_commentedmost_likednewestrelevance
limitbody.paramsinteger (1–30)No20

Code samples

bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "xiaohongshu",
  "action": "trending",
  "params": {}
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json
{
  "id": "req_…",
  "platform": "xiaohongshu",
  "action": "trending",
  "results": [
    {
      "id": …,
      "url": …,
      "title": …,
      "author_name": …,
      "is_video": …,
      "image_url": …,
      "platform": …
    }
  ],
  "count": …,
  "billing": { … },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.

FieldMeaning
idThe record's unique ID on the source platform. Unique only within one platform; IDs can repeat across platforms.
urlLink to the record on the source platform.
titleTitle. null when the platform has no titles (for example text-only posts).
author_nameAuthor's display name.
is_videoWhether the item is a video.
image_urlImage link. Capabilities with several images may return an image_urls array.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401
Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422
Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402
Insufficient balance. Top up first.
429
Per-minute request limit reached. Wait for Retry-After and try again.
503
Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty
The request completed without data and is not charged (billing.reason = empty_result_refunded).