Co APIkaskus.co.id ↗
Access Kaskus.co.id forum data via 5 endpoints. Fetch hot threads, search by keyword, read post content, and explore community listings with author and vote metadata.
What is the Co API?
The Kaskus API provides structured access to Indonesia's largest online forum through 5 endpoints covering threads, posts, communities, and search. get_hot_threads returns paginated thread feeds with full first-post content, while get_thread_posts exposes per-post user info, vote metadata, and content in plain text, HTML, and BBCode formats. Community discovery, keyword search, and feed filtering are all supported.
curl -X GET 'https://api.parse.bot/scraper/b159dbb9-02a2-444c-90bc-80dd6a712701/get_hot_threads?limit=5&feed_type=active&channel_id=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 kaskus-co-id-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.kaskus_forum_api import Kaskus, FeedType, PostSort
kaskus = Kaskus()
# Discover popular communities
for community in kaskus.communities.list():
print(community.name, community.meta.total_threads, community.meta.total_members)
# Browse hot threads with active feed type
for thread in kaskus.threads.hot(feed_type=FeedType.ACTIVE, limit=10):
print(thread.title, thread.meta.total_views, thread.meta.total_replies)
# Search threads by keyword
for thread in kaskus.threads.search(query="teknologi", limit=5):
print(thread.title, thread.community.name)
# Get a community by ID and browse its threads
games = kaskus.community(id="44")
for thread in games.threads(feed_type=FeedType.HOT, limit=5):
print(thread.title, thread.thread_starter.display_name)
# Read posts in the thread
for post in thread.posts.list(sort=PostSort.NEWEST, limit=3):
print(post.user.display_name, post.content.text, post.dateline)
Fetch hot or active threads from Kaskus. Supports pagination via cursor and filtering by feed type or channel. Returns thread objects with full first post content, community metadata, and engagement stats. Each thread includes title, slug, thread_starter, first_post (with content in text/html/bbcode), and meta (total_views, total_replies). Paginate by passing the next_cursor value from a previous response.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of threads to return per page. |
| cursor | string | Pagination cursor from a previous response's next_cursor field. |
| feed_type | string | Type of feed to retrieve. |
| channel_id | integer | Channel ID to filter threads (0 for all channels). Use get_popular_communities to discover valid IDs. |
{
"type": "object",
"fields": {
"data": "array of thread objects each containing id, title, slug, community (id, name, icon, meta), thread_starter (id, display_name, username, avatar), first_post (content with text/html/bbcode, dateline, user with reputation_info), meta (total_views, total_replies)"
},
"sample": {
"data": {
"data": [
{
"id": "6a28c93320ddfc2e9f0a94d7",
"meta": {
"total_views": 151,
"total_replies": 2
},
"slug": "diskusi-steam-summer-sale-sebentar-lagi-udah-siapin-budget-belum",
"type": 1,
"title": "[DISKUSI] Steam Summer Sale Sebentar Lagi, Udah Siapin Budget Belum?",
"community": {
"id": "44",
"icon": {
"url": "https://s.kaskus.id/ficon/image-44.png"
},
"meta": {
"total_posts": 870961,
"total_members": 28170,
"total_threads": 40915
},
"name": "Games"
},
"first_post": {
"id": "6a28c93320ddfc2e9f0a94d8",
"content": {
"text": "Nggak kerasa Steam Summer Sale udah makin dekat lagi...",
"snippet": "Nggak kerasa Steam Summer Sale udah makin dekat lagi..."
},
"dateline": 1781057843
},
"thread_starter": {
"id": "11815849",
"username": "yearly123",
"display_name": "yearly123"
}
}
]
},
"status": "success"
}
}About the Co API
Thread Feeds and Search
get_hot_threads accepts a feed_type parameter ('hot' or 'active'), an optional channel_id to scope results, and a cursor string for pagination. Each returned thread object includes id, title, slug, community, thread_starter, and a first_post object with content in text, HTML, and BBCode. search_threads takes a required query string and returns the same thread shape for keyword-matched results, also supporting cursor-based pagination.
Post-Level Detail
get_thread_posts fetches the full reply sequence for a given thread_id. Posts include id, a Unix dateline timestamp, and a user object with display_name, username, avatar, and reputation_info. Content is provided in multiple formats. A sort parameter accepts 'newest' or 'oldest', and pagination is handled via page and limit.
Community Discovery
get_popular_communities returns communities ranked by activity, each with id, name, description, icon, and a meta block containing total_threads, total_members, and total_posts. The channel_id parameter scopes results; verified working values include 0 (all) and 10. These IDs feed directly into get_community_threads, which scopes the thread feed to a single community and accepts the same feed_type and cursor inputs as the global hot-threads endpoint. Note that not all community IDs are valid as channel_id filter values in get_hot_threads; invalid values may return an upstream error.
The Co API is a managed, monitored endpoint for kaskus.co.id — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when kaskus.co.id 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 kaskus.co.id 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?+
- Track trending Indonesian forum discussions by polling
get_hot_threadswithfeed_type: 'hot'on a schedule. - Build a keyword monitor for brand or topic mentions using
search_threadswith a product or keyword query. - Aggregate community-level activity stats (total_threads, total_members, total_posts) from
get_popular_communitiesfor forum analytics. - Reconstruct full thread conversations including reply order and user reputation data via
get_thread_posts. - Identify active sub-communities by comparing
meta.total_postsacross results fromget_popular_communities. - Feed Kaskus thread content into NLP pipelines using the plain-text content field from post objects.
- Scope a content dashboard to a specific community by pairing
get_popular_communitiesIDs withget_community_threads.
| 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 Kaskus have an official developer API?+
What does `get_thread_posts` return beyond the post text?+
display_name, username, avatar URL, and reputation_info, along with a Unix dateline timestamp and content in multiple formats (text, HTML, BBCode). You can sort results by 'newest' or 'oldest' and paginate using the page and limit parameters.Are there any quirks with the `channel_id` filter in `get_hot_threads`?+
get_popular_communities are valid as channel_id values in get_hot_threads. Passing an unsupported ID may return an upstream error. Verified working values are 0 (all channels) and 10. Test IDs individually before relying on them in production.Does the API expose private threads, login-gated boards, or user inbox data?+
Is there a way to fetch threads from a community that doesn't appear in `get_popular_communities`?+
get_popular_communities, and get_community_threads requires a community_id from that list. Communities not ranked in that feed are not directly discoverable through the existing endpoints. You can fork this API on Parse and revise it to add a community lookup or direct-ID endpoint.