Discover/Hsoub API
live

Hsoub APIio.hsoub.com ↗

Access Hsoub I/O community posts and full comment threads. Returns post summaries, body text, author profiles, avatars, and nested comments via 2 endpoints.

Endpoint health
monitored
get_post_comments
list_latest_posts
Checks pendingself-healing
Endpoints
2
Updated
2h ago

What is the Hsoub API?

The Hsoub I/O API exposes 2 endpoints for reading content from io.hsoub.com, an Arabic-language developer community. The list_latest_posts endpoint returns paginated post summaries — up to 200 posts across 8 pages — including post IDs, titles, canonical URLs, and author metadata. The get_post_comments endpoint fetches a single post's full body and its complete nested comment thread in one request, with per-comment fields including points, depth, and author avatars.

This call costs2 credits / call— charged only on success
Try it
1-based page of 25 posts; integer from 1 to 8.
→ api.parse.bot/scraper/d3782a72-90c3-43e2-a205-455e961e74d5/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/d3782a72-90c3-43e2-a205-455e961e74d5/list_latest_posts?page=3' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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 io-hsoub-com-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.

"""Walkthrough: Hsoub I/O SDK — browse latest posts and read comments."""
from parse_apis.io_hsoub_com_api import HsoubIO, PostNotFound

client = HsoubIO()

# Browse the latest posts on the community feed, capped at 5.
for post in client.posts.list(limit=5):
    print(post.title, f"({post.community_name}) — {post.points} pts, {post.comment_count} comments")

# Drill into the first post's comment thread.
post = client.posts.list(limit=1).first()
if post is not None:
    print(f"\nComments on: {post.title}")
    for comment in post.comments.list(limit=10):
        indent = "  " * comment.depth
        print(f"{indent}{comment.display_name}: {comment.body_text[:80]}")

    # A deleted or non-existent post raises PostNotFound.
    try:
        # Re-fetch comments to show error handling on a stale reference.
        for c in post.comments.list(limit=3):
            pass
    except PostNotFound as e:
        print(f"Post gone: {e.message}")

print("\nexercised: posts.list / comments.list")
All endpoints · 2 totalmissing one? ·

Returns the site's 'latest' (الأحدث) post feed, 25 posts per page in the site's own newest-first order. Each row is one post summary: numeric post_id, title, canonical URL, community slug/name (null for posts outside a community), author username/display name/profile URL (null when the site shows no author), ISO-8601 published_at (UTC), vote points, comment_count and a text excerpt. Pagination: page defaults to 1; the site paginates by excluding already-seen posts, so page N costs N round trips and page is capped at 8 (200 posts). has_more/next_page describe continuation inside that cap. A page beyond the feed's end returns an empty posts array.

Input
ParamTypeDescription
pageinteger1-based page of 25 posts; integer from 1 to 8.
Response
{
  "type": "object",
  "fields": {
    "page": "integer page requested",
    "posts": "array of post summaries: post_id, title, url, community_slug, community_name, author_username, author_display_name, author_url, published_at, points, comment_count, excerpt",
    "has_more": "boolean, true when another page is available within the page cap",
    "next_page": "integer page to request next, or null",
    "page_size": "integer, always 25"
  },
  "sample": {
    "data": {
      "page": 1,
      "posts": [
        {
          "url": "https://io.hsoub.com/webdev/185887-%D8%B2%D8%A7%D9%88%D9%85%D9%88",
          "title": "زاومو ضيف لحظة وخلي الناس اتضيف زوايا",
          "points": 0,
          "excerpt": "فكرة زاومو هو تطبيق يحتوي على لحظات...",
          "post_id": "185887",
          "author_url": "https://io.hsoub.com/u/12ayesh",
          "published_at": "2026-10-14T09:27:33+00:00",
          "comment_count": 0,
          "community_name": "تطوير الويب",
          "community_slug": "webdev",
          "author_username": "12ayesh",
          "author_display_name": "12Ayesh"
        }
      ],
      "has_more": true,
      "next_page": 2,
      "page_size": 25
    },
    "status": "success"
  }
}

About the Hsoub API

Post Feed

The list_latest_posts endpoint returns the site's newest-first feed in pages of 25 posts. The page parameter accepts integers from 1 to 8, and the response includes a has_more boolean and a next_page integer to drive pagination. Each post summary carries a numeric post_id, title, url, community_slug, community_name, and author fields (author_username, author_display_name, author_url). Community fields are null for posts outside a named community.

Post Detail and Comments

The get_post_comments endpoint accepts a post_id string — as emitted by list_latest_posts — and returns both the full post object and its entire comment thread in a single response. The post object includes body_text, published_at, author_avatar_url, and author_url. Because the site renders all comments on a single page, no comment pagination is needed; the response delivers every comment at once alongside a comment_count integer.

Comment Structure

Each comment in the comments array includes comment_id, parent_comment_id, and depth fields that together describe the thread hierarchy. Additional per-comment fields cover username, display_name, profile_url, avatar_url, published_at, points, and body text. This makes it straightforward to reconstruct threaded discussions or compute engagement metrics without additional requests.

Reliability & maintenance

The Hsoub API is a managed, monitored endpoint for io.hsoub.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when io.hsoub.com 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 io.hsoub.com 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?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitor trending topics on the Hsoub I/O community by polling list_latest_posts and tracking new post titles and community slugs over time.
  • Build an Arabic developer content aggregator using title, url, and community_name from the post feed.
  • Analyze comment engagement by comparing points and comment_count across posts fetched with get_post_comments.
  • Reconstruct nested discussion threads using parent_comment_id and depth fields from the comments array.
  • Profile active community contributors by aggregating author_username and author_url across multiple pages of posts.
  • Track author activity over time by combining published_at timestamps from both post and comment responses.
  • Display post summaries with author avatars in a third-party reader app using author_avatar_url from get_post_comments.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Hsoub I/O have an official developer API?+
Hsoub I/O does not publish an official public developer API for io.hsoub.com. This Parse API is the available programmatic option for accessing its post and comment data.
What does `get_post_comments` return for a post with no comments?+
The endpoint still returns the full post object — including body_text, author_avatar_url, and published_at — along with an empty comments array and a comment_count of 0.
How far back does `list_latest_posts` go?+
The endpoint covers up to 8 pages of 25 posts each (200 posts total) in newest-first order. Posts beyond that window are not accessible through this endpoint. You can fork this API on Parse and revise it to extend the page cap or target a specific community feed.
Can I search posts by keyword or filter by community?+
Not currently. The list_latest_posts endpoint returns the site-wide latest feed without keyword search or community filtering. You can fork this API on Parse and revise it to add a search or community-scoped endpoint.
Does the API return vote counts or view counts on posts from the feed?+
The post summary objects from list_latest_posts do not include vote or view counts; those fields are not part of the feed response. Per-comment points are available from get_post_comments, but post-level vote or view metrics are not currently exposed. You can fork this API on Parse and revise it to add those fields if the source makes them available.
Page content last updated . Spec covers 2 endpoints from io.hsoub.com.
Related APIs in Social MediaSee all →
reddit.com API
Search Reddit posts and comments across any subreddit. Retrieve post discussions with full comment threads, search by keyword, and browse subreddit feeds by category (hot, new, top, rising) with flexible sorting and pagination.
news.ycombinator.com API
Browse Hacker News top/new/best/ask/show stories and job posts, search stories by keyword and timeframe, fetch user profiles, retrieve comment threads for a post, and compute basic engagement stats and trending stories.
dev.to API
Access data from dev.to.
pikabu.ru API
Access trending and fresh content from Pikabu's Russian community platform, including hot posts, best posts, and community-specific stories with their full comment threads. Build applications powered by user profiles and detailed post data from one of Russia's most popular social communities.
x.com API
Retrieve posts and profile information from X (Twitter) user timelines by specifying a username. Access live post data, engagement metrics, and user profile details for any public account.
liuguiyu.github.io API
Discover and read blog articles on cybersecurity, identity management, AI, and emerging technology trends from a personal tech blog. Browse through the complete collection of posts or dive into individual articles to stay updated on the latest insights in CIAM and digital security.
oneleet.com API
Access data from oneleet.com.
superuser.com API
Access questions, answers, and comments from Super User to find solutions to technical problems, search for specific topics, and explore trending discussions across the community. View user profiles, track site activity, and discover the hottest questions trending across the Stack Exchange network.