List a Reddit user's posts
Returns the posts a Reddit account has submitted, newest first by default, up to 25 per page. Each row carries the title, the body at ext.selftext, the score, the comment count, the upvote ratio, the flair, Reddit's own content language, the author avatar, structured media at content.media_urls and the permalink. ext.subreddit is the field that matters most on this lane and is populated on every row: a person's submissions span communities by construction, so it is the only thing that says where each post landed. Paginate with cursor from the previous response's pagination.next_cursor. post.engagement.shares is null here, as on every Reddit list endpoint — the upstream sends a share-BUTTON count on this shape and that is a different metric from the crosspost count this field means, so it is not published. An account with no submissions returns an empty list and is refunded; an account that does not exist is indistinguishable from one with no posts on this upstream and returns the same empty list, so check /v1/reddit/profile when you need to tell them apart. When the main source is unavailable, the first page in the default order is answered by a second source: the same posts, with author.avatar_url and ext.content_language null and no next cursor. A later page, sort=hot, sort=top or a timeframe has no second source and returns an error to retry.
Request
- Base URL: https://www.socialcrawl.dev/v1
- URL: https://www.socialcrawl.dev/v1/reddit/profile/posts
- Auth: API key in header x-api-key
Query parameters
Reddit username without the u/ prefix. Case-insensitive.
Sort order for the account's submissions. top defaults to the all-time window; pass timeframe to narrow it.
Only return posts from this window. Applied on sort=top. Omitted sort=top is treated as timeframe=all so the documented call is not an empty page.
Cursor to get more results. Get 'cursor' from the previous response.
Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off the page, and the page that reaches one ends the walk: next_cursor is not returned and pagination.stopped_at is since. Sending it sets the newest-first sort shown in this endpoint's sort parameter (any other sort value is a free 400). The page still costs what a page costs, so you pay for the pages you walk and no more. A row with no date is kept. published_after, start_date, from_date, publish_time (yesterday, this-week, this-month, last-3-months, last-6-months) and max_age_days are accepted and applied as since.
Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. published_before, end_date and to_date are accepted and applied as until.
Headers
Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.
Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.
Response
Successful response
Example response
{
"success": true,
"platform": "reddit",
"endpoint": "/v1/reddit/profile/posts",
"credits_used": 1,
"credits_remaining": 4999,
"request_id": "req-abc123",
"idempotent_replay": true,
"meta": {
"hint": {
"code": "search_multi",
"message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
"method": "GET",
"path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
}
},
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
"has_more": true,
"page_size": 30,
"stopped_at": "known_id"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.