Reddit Search API for historical discussions

Build search interfaces for archived Reddit posts and comments. Explore filters, bounded retrieval and request-based pricing through an independent historical API.

Get API key

Request example

cURL

curl --fail-with-body -H "Authorization: Bearer YOUR_API_KEY" "https://api.redditsearchapi.com/v1/search?q=quantization&subreddit=LocalLLaMA&limit=3"

Give your search interface a defined scope

Reddit Search API helps application developers retrieve archived posts and comments through a read-only HTTP interface. This is an independent historical archive, not an official Reddit service or a live feed. Use it when your product needs a search view over past discussions, with an explanation of what a particular query requested. Historical access does not establish complete coverage, permanent record availability or reproducible results across repeated requests.

A useful search interface starts with a question rather than an unrestricted collection job. Let a reader choose a topic, a community and a date interval, then show those choices alongside the returned material. A query about battery repair in one community answers a different question from the same phrase across several communities. Preserve that distinction in your application instead of presenting every returned record as evidence about Reddit as a whole.

Retrieve records without promising a complete conversation

Requests to api.redditsearchapi.com return JSON records. The search route accepts q, subreddit, author, kind, from, to and min_score, together with limit and page. The kind values are post and comment. Date boundaries use UTC dates in YYYY-MM-DD format, with to inclusive. Minimum score narrows eligibility; it does not rank the response. Results follow archive document order rather than chronological, relevance or score order.

Each request returns at most 100 records, and each query permits at most 100 pages. Reaching the last allowed page does not prove that every matching record was retrieved. Records are flat; when parent_id or link_id is present, your application may group available items locally. That operation cannot restore missing ancestors or establish a complete thread. Make these limits visible wherever a reader could mistake a partial result set for comprehensive coverage.

Start with a key and budget successful requests

Register with email and a password of 12–72 bytes. The key appears once immediately after signup, before payment. An optional 100-credit trial depends on network-wide anti-abuse eligibility. A successful retrieval costs one credit even when it returns no records. The price is $1 per 1,000 successful requests; the $50 minimum paid top-up buys 50,000 credits. Paid credits do not expire, and there is no subscription.

Paid funding starts with an invoice in your signed-in account panel. Use its exact amount and recipient for USDT on TRON TRC20 or USDC on Ethereum mainnet ERC20, then submit the transaction hash for verification. Only a confirmed genuine transfer adds credit; settlement speed is not guaranteed. The documentation explains 401, 402 and 429 responses. Public /v1/status reports scope and HTTP responsiveness, not search-backend health or archive completeness.