POST /api/xiaohongshu/notes
Price: 20 credits
Get Xiaohongshu (RED, 小红书) note details by note ID or full note URL
Get full details of a Xiaohongshu (RED, 小红书) note by note ID or note URL. Returns type (video/normal), title, text, hashtags, mentions, images, video, author, created time, like/collect/comment/share counts. A note ID requires an xsec_token (present in note/feed/search URLs).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)note string required — Xiaohongshu note ID ('64b8140a0000000016027186') or full note URL. When a bare note ID is given, xsec_token is required. (examples: "https://www.xiaohongshu.com/explore/64b8140a0000000016027186?xsec_token=AB_yBVYPZ09gPsXTE6JBbohIwoiaw3RXja90dH-LsHrnk=", "64b8140a0000000016027186"; minLength: 1; pattern: ^(?:https?://[^\s]+|[0-9a-fA-F]{24})$)xsec_token string nullable — Access token bound to the note, found in note/feed/search URLs. Required for a bare note ID.@type string (default: "XiaohongshuNote")id string requiredtype string nullabletext string nullablehashtags array (default: [])mentions array (default: [])@type string (default: "XiaohongshuUser")id string requirednickname string nullablered_id string nullableimage string nullablexsec_token string nullableprofile_url string nullableimages array (default: [])video object nullable@type string (default: "XiaohongshuNoteVideo")play_url string nullableduration integer nullablewidth integer nullableheight integer nullableauthor object nullable@type string (default: "XiaohongshuUser")id string requirednickname string nullablered_id string nullableimage string nullablexsec_token string nullableprofile_url string nullablecreated_at integer nullablelast_update_at integer nullableip_location string nullablelike_count integer nullablecollect_count integer nullablecomment_count integer nullableshare_count integer nullablenote_url string nullablexsec_token string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Note not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.