Juejin APIjuejin.cn ↗
Access Juejin's recommended article feed, keyword search, and full markdown article content via a structured REST API. Includes views, likes, tags, and author data.
What is the Juejin API?
The Juejin API exposes 3 endpoints covering the article feed, keyword search, and full article retrieval from juejin.cn, a Chinese technical community. The get_article endpoint returns the complete article body in markdown format alongside metadata including view counts, like counts, comment counts, and tags. The list_articles endpoint delivers paginated feed results sorted by Juejin's recommendation algorithm, and search_articles accepts a keyword query to find relevant posts.
curl -X GET 'https://api.parse.bot/scraper/7954f671-42f8-4569-99a6-b9cb7bfbc220/list_articles?limit=5&cursor=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace juejin-cn-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.juejin_scraper_api import Juejin, Article, ArticleSummary
client = Juejin()
# Browse recommended articles
for article in client.articlesummaries.list(limit=3):
print(article.title, article.author, article.views, article.likes)
# Search for Python-related articles and drill into details
for result in client.articlesummaries.search(query="Python", limit=2):
print(result.title, result.publication_date, result.tags)
full = result.details()
print(full.content, full.author_id)
Get a feed of recommended articles from Juejin. Returns paginated results sorted by recommendation algorithm. Each article includes basic metadata (title, author, tags, engagement counts). Use the cursor from a previous response to advance pages.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of articles to return per page. |
| cursor | string | Pagination cursor returned from a previous call. Use "0" to start from the beginning. |
{
"type": "object",
"fields": {
"cursor": "string pagination cursor for the next page",
"articles": "array of article summary objects with id, title, author, author_id, publication_date, tags, views, likes, comments, url",
"has_more": "boolean indicating whether more pages are available"
},
"sample": {
"data": {
"cursor": "1",
"articles": [
{
"id": "7584110439933100078",
"url": "https://juejin.cn/post/7584110439933100078",
"tags": [
"Cursor",
"AI编程",
"程序员"
],
"likes": 667,
"title": "全面封禁 Cursor！又一家大厂出手了",
"views": 188845,
"author": "程序员鱼皮",
"comments": 227,
"author_id": "2444938365386621",
"publication_date": "2025-12-16T07:43:19"
}
],
"has_more": true
},
"status": "success"
}
}About the Juejin API
Endpoints and Response Data
The list_articles endpoint returns a paginated feed of recommended articles from Juejin. Each article object includes id, title, author, author_id, publication_date, tags, views, likes, comments, and url. Pagination is cursor-based: pass cursor: "0" to start from the beginning, and use the returned cursor value with subsequent calls. The has_more boolean tells you when you've reached the end of the feed.
search_articles accepts a required query string and returns results ordered by relevance. The response shape mirrors list_articles — the same article summary fields, plus cursor and has_more for pagination. Use this endpoint to retrieve articles on a specific technology, framework, or topic published to the Juejin community.
Full Article Content
get_article takes a numeric article_id (obtainable from list_articles or search_articles results) and returns the complete article. The content field contains the full body in markdown format, making it straightforward to parse headings, code blocks, and links. Additional fields include tags (array of strings), views, likes, comments, author, author_id, url, and id. This endpoint is the primary way to retrieve substantive technical content — the feed and search endpoints return summaries only.
Coverage and Language
Juejin is a Chinese-language developer community covering topics like frontend development, backend engineering, cloud infrastructure, mobile development, and data science. Articles are predominantly written in Chinese. The platform hosts content from individual developers, open-source project teams, and corporate engineering blogs. There is no language filtering parameter in the current API.
The Juejin API is a managed, monitored endpoint for juejin.cn — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when juejin.cn changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official juejin.cn API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate trending technical articles from the Chinese developer community by polling
list_articlesand trackingviewsandlikesover time. - Build a topic monitor that uses
search_articleswith specific technology keywords (e.g., 'React', 'Kubernetes') to surface recent Chinese-language posts. - Extract full markdown content from articles via
get_articleto build a translated technical knowledge base. - Collect author-level metadata —
author_id, article counts, and engagement signals — across search results for developer research. - Index article
tagsfrom feed results to map which technologies are trending on Juejin at a given time. - Create a content pipeline that fetches article IDs from
search_articlesand retrieves full text viaget_articlefor NLP analysis or summarization. - Track comment and like counts on specific articles by periodically calling
get_articlewith the samearticle_id.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Juejin have an official developer API?+
What does `list_articles` return versus `get_article`?+
list_articles returns article summaries: id, title, author, author_id, publication_date, tags, views, likes, comments, and url. It does not include the article body. get_article accepts an article_id and returns the full content field in markdown format, along with all the same metadata fields. To read article text, you need to call get_article using an ID from the feed or search results.How does pagination work across the feed and search endpoints?+
list_articles and search_articles use cursor-based pagination. Pass cursor: "0" on the first request. Each response returns a cursor string and a has_more boolean. If has_more is true, pass the returned cursor value in your next request to retrieve the following page. There is no page-number or offset parameter.Can I retrieve user profiles or author follower counts through this API?+
Does the API expose article publication dates in the search results?+
list_articles and search_articles return a publication_date field in each article summary object. The get_article endpoint does not separately document a publication date field — if you need the date alongside full content, retrieve it from the summary before calling get_article.