Reddit User Post Rank Scraper
ScraperAPI
$1/1000
results
Reddit User Post Rank Scraper
ScraperAPI
Find a user post rank inside a subreddit via DataDoping Reddit API.
$1/1000results
Try it out$1/1000
results
Find a user post rank inside a subreddit via DataDoping Reddit API.
The Reddit User Post Rank Scraper locates a Reddit user’s posts inside a target subreddit and returns ranking-oriented results as flattened JSON. Provide a username and subreddit, choose listing sort (hot, new, top, rising), and optionally a time window for Top — then get structured rows describing how that user’s posts appear in the scanned listing.
Built for community analysts, mods, growth teams, and researchers measuring a creator’s footprint inside a specific community. Unlike general user-post scrapers, this tool is scoped to one username + one subreddit for ranking context.
Returns clean, structured JSON (flattened nested fields) with scan totals and per-post rank details when posts are found.
u/ / r/ forms accepted)hot, new, top, rising (also accepts controversial)The Reddit User Post Rank Scraper locates a Reddit user’s posts inside a target subreddit and returns ranking-oriented results as flattened JSON. Provide a username and subreddit, choose listing sort (hot, new, top, rising), and optionally a time window for Top — then get structured rows describing how that user’s posts appear in the scanned listing.
Built for community analysts, mods, growth teams, and researchers measuring a creator’s footprint inside a specific community. Unlike general user-post scrapers, this tool is scoped to one username + one subreddit for ranking context.
Returns clean, structured JSON (flattened nested fields) with scan totals and per-post rank details when posts are found.
u/ / r/ forms accepted)hot, new, top, rising (also accepts controversial)| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| username | string | Yes | — | Reddit username to rank. |
| subreddit | string | Yes | — | Subreddit to search within. |
| sort | string | No | "hot" | Listing sort: hot, new, top, rising. |
| time | string | No | "all" | Time range when sort is top. |
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| username | string | Yes | — | Reddit username to rank. |
| subreddit | string | Yes | — | Subreddit to search within. |
| sort | string | No | "hot" | Listing sort: hot, new, top, rising. |
| time | string | No | "all" | Time range when sort is top. |
How parameters affect the run: sort and time change which listing slice is scanned and therefore which ranks appear. Results are specific to that username/subreddit pair.
How parameters affect the run: sort and time change which listing slice is scanned and therefore which ranks appear. Results are specific to that username/subreddit pair.
{
"username": "spez",
"subreddit": "announcements",
"sort": "top",
"time": "year"
}
{
"username": "spez",
"subreddit": "announcements",
"sort": "top",
"time": "year"
}
Rows are flattened objects. Base fields always include:
Rows are flattened objects. Base fields always include:
| Field | Type | Description |
|---|---|---|
| username | string | Requested username |
| subreddit | string | Requested subreddit |
| sort | string | Sort used |
| time | string | Time range used |
| totalPostsScanned | number | null | Posts scanned in the ranking pass |
| userPostsFound | number | null | How many of the user’s posts were found |
| Field | Type | Description |
|---|---|---|
| username | string | Requested username |
| subreddit | string | Requested subreddit |
| sort | string | Sort used |
| time | string | Time range used |
| totalPostsScanned | number | null | Posts scanned in the ranking pass |
| userPostsFound | number | null | How many of the user’s posts were found |
When matching posts exist, each row also includes flattened post fields from the API (for example id, title, score, rank, permalink-like keys — exact keys depend on the upstream payload and are flattened with dot notation for nested objects).
When matching posts exist, each row also includes flattened post fields from the API (for example id, title, score, rank, permalink-like keys — exact keys depend on the upstream payload and are flattened with dot notation for nested objects).
When no posts are found, a single summary row is emitted with base metrics and any remaining summary fields from the API.
When no posts are found, a single summary row is emitted with base metrics and any remaining summary fields from the API.
Optional fields may be null when the API omits them.
Optional fields may be null when the API omits them.
{
"username": "spez",
"subreddit": "announcements",
"sort": "top",
"time": "year",
"totalPostsScanned": 250,
"userPostsFound": 3,
"id": "1ab9999",
"title": "Updates on site reliability this quarter",
"score": 22100,
"num_comments": 4300,
"rank": 2,
"permalink": "/r/announcements/comments/1ab9999/updates_on_site_reliability_this_quarter/"
}
{
"username": "spez",
"subreddit": "announcements",
"sort": "top",
"time": "year",
"totalPostsScanned": 250,
"userPostsFound": 3,
"id": "1ab9999",
"title": "Updates on site reliability this quarter",
"score": 22100,
"num_comments": 4300,
"rank": 2,
"permalink": "/r/announcements/comments/1ab9999/updates_on_site_reliability_this_quarter/"
}
Field names beyond the base metrics may vary slightly with the API payload; nested objects are flattened (e.g.
preview.images→ stringified / dotted keys).
Field names beyond the base metrics may vary slightly with the API payload; nested objects are flattened (e.g.
preview.images→ stringified / dotted keys).