The reddit tag includes post lookup by ID or permalink, post search, subreddit posts, user posts, and user activity. The exact paths and query parameters are generated in the API Reference; all are read-only GET operations.
Choose an operation
Use GET /v1/reddit/search_posts with query to search public posts. Its optional parameters are sort and limit. To read a subreddit feed, use GET /v1/reddit/subreddit_posts/{subreddit}. The path parameter is subreddit, and the contract declares category, time_filter, and limit as optional query parameters.
For one post, use GET /v1/reddit/post_by_id/{id} with its id path parameter, or GET /v1/reddit/post_by_permalink with the permalink query parameter. User-focused reads are GET /v1/reddit/user_activity/{username} and GET /v1/reddit/user_posts/{username}. Both identify the account with username; user activity accepts limit, while user posts accepts category, time_filter, and limit. The API Reference is the source for operation schemas and for the exact data returned by each read.
Make a request
Keep REPLYNODES_API_KEY in a secret store and send it only with the request. This request searches posts by query:
curl -sS \
-H "Authorization: Bearer $REPLYNODES_API_KEY" \
"https://api.replynodes.com/v1/reddit/search_posts?query=public%20data"The HTTP API returns successful responses in the { data, meta } envelope. Preserve meta.request_id when correlating a request with support. See Quickstart for the common request pattern, Search for web search, and the API Reference for complete parameter and response details.
Use post lookup when an agent already has an identifier or permalink, and use search when the topic or phrase is known but the post is not. Subreddit and user routes provide bounded timelines for a named community or public account. Keep the original permalink, subreddit, or username in the job record so the result can be reproduced and so similarly named communities are not silently substituted. Search and activity results are public upstream data and may change as posts are edited, removed, ranked, or made unavailable; a response is therefore a point-in-time observation rather than a permanent archive.
The API Reference is authoritative for path templates, pagination, limits, and response fields. Do not add OAuth credentials, cookies, sessions, or private-account assumptions to a client: this surface is intentionally read-only and fail-closed when the upstream cannot provide public data. Preserve the returned request_id for diagnostics. For transient failures, follow the response status and any Retry-After value with a bounded retry policy; do not turn a research request into an unbounded crawl or a high-volume replay.