/juejin/articles/search

POST /api/juejin/articles/search

Price: 5 credits

Search Juejin articles by text, sorted by relevance, newest or hottest: title, summary, cover, author, category, tags, and view, like, bookmark and comment counts

How to use it

Without `period`, Juejin search answers with loosely matching articles, even for nonsense text. Rows carry no body — pass an `id` to juejin/articles for it.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search text (examples: "python", "React Hooks"; minLength: 1)
• count integer required — Max number of articles to return (min: 1; max: 250)
• sort string — Order of the results: by relevance, newest first or hottest first (default: "relevance"; one of: "relevance", "newest", "hottest")
• period string — Only articles published within the last day, week or three months (default: "any"; one of: "any", "day", "week", "quarter")

Response

• @type string (default: "JuejinArticleRow")
• id string required
• url string nullable
• brief string nullable
• cover string nullable
• original_url string nullable
• original_author string nullable
• is_original boolean nullable
• view_count integer nullable
• like_count integer nullable
• bookmark_count integer nullable
• comment_count integer nullable
• hot_index integer nullable
• word_count integer nullable
• read_time_minutes integer nullable
• created_at integer nullable
• published_at integer nullable
• updated_at integer nullable
• category object nullable
  • @type string (default: "JuejinCategoryRef")
  • id string required
  • name string nullable
  • alias string nullable
• tags array (default: [])
  • @type string (default: "JuejinTag")
  • id string required
  • name string nullable
  • url string nullable
  • icon string nullable
  • color string nullable
  • alternative_name string nullable
  • article_count integer nullable
  • follower_count integer nullable
  • created_at integer nullable
  • updated_at integer nullable
• themes array (default: [])
  • @type string (default: "JuejinTheme")
  • id string required
  • name string nullable
• author object nullable
  • @type string (default: "JuejinAuthor")
  • id string required
  • name string nullable
  • url string nullable
  • image string nullable
  • job_title string nullable
  • company string nullable
  • description string nullable
  • level integer nullable
  • power integer nullable
  • follower_count integer nullable
  • article_count integer nullable
  • likes_received integer nullable
  • views_received integer nullable

Errors

• 422 — 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 — The entity was not found, or a precondition failed 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.