Compare How Communities Discuss Soil

Explore soil discussions in gardening, then compare bounded community samples with matched archive filters. Independent historical Reddit data for community researchers.

Get API key

Request example

cURL

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

Community query workspace

This local list contains query targets, not a verified archive inventory. Gardening is an example; records may be absent. Matching filters do not establish equal coverage or representative samples.

Names are grouped alphabetically on this page only. An inactive letter says nothing about the archive.

Local query targets

G

gardening

Request previews only: q=soil and limit=3 stay fixed. Nothing is sent to the API. No key is requested or saved.

First request: gardening

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

Add a different community name to prepare a second, separate request.

Second request:

Get API key

Start with three gardening records

Subreddit API gives community researchers read access to an independent historical Reddit archive. It is not affiliated with Reddit and does not supply live updates. Use it to collect a bounded selection of stored discussions before comparing language between communities. A retrieved post need not reflect the current original page, and the archive does not guarantee complete coverage or continued availability.

Start with GET https://api.subredditapi.com/v1/search?q=soil&subreddit=gardening&limit=3. q=soil supplies the search text, subreddit=gardening selects one community, and limit=3 requests at most three records. Send your own credential through X-API-Key: <key> or Authorization: Bearer <key>; <key> is a placeholder. The response may contain fewer records or none. An empty success still costs one credit.

Synthetic response excerpt, not a real result: {"data":[],"pagination":{"page":1,"limit":3,"total":0,"relation":"eq"},"credits":{"cost":1,"balance":99}}. The balance is fictional. This demonstrates the response container without inventing actual gardening content. Inspect the records you receive before defining text-coding rules. Do not interpret a small sample or an empty response as a census of the community or its opinions.

Compare selections rather than entire communities

Choose a second community for which relevant archived records are available, then send a separate request changing subreddit. Hold the search text, record kind, dates and any score threshold constant where appropriate. Matching filters makes the selection method easier to explain; it does not equalize archive coverage or remove page-cap bias. The API does not accept a list of communities in one subreddit value.

Read the returned text locally and define categories for your question, such as soil preparation, drainage or compost. These are proposed research labels, not observed findings or built-in API classifications. Distinguish what a passage says from your interpretation, and record ambiguous cases. Word counts, coding and sentiment analysis belong to your own tools; the service provides retrieval, not a custom analytics endpoint.

Responses are flat records. If parent_id or link_id is present, you can group received items locally, but missing ancestors and incomplete conversations remain possible. Results follow internal _doc order, not time, relevance or score. Each request returns up to 100 records and page is limited to 1 through 100. Neither pagination nor partitioning proves complete or duplicate-free collection.

Plan access and the request budget

Each successful retrieval costs one credit, including empty results: $1 per 1000 requests. A minimum paid top-up of $50 buys 50000 credits. There is no subscription and paid credits do not expire. Signup displays the key once before payment. An optional 100-credit trial depends on network-wide anti-abuse eligibility and is not guaranteed. Keys and balances belong to subredditapi.com.

For paid credit, sign in and create an invoice before transferring funds. Use its receiving address and exact amount with USDT on TRON TRC20 or USDC ERC20 on Ethereum mainnet. Submit the payment transaction hash and request verification. Credit requires a confirmed genuine transfer verified by the server, with no fixed crediting time. A unique invoice does not imply a new wallet address.

Invalid requests do not debit credits; upstream failures refund reservations. A client connection failure may follow a billable server success, and another successful attempt costs another credit. The public /v1/status route is uncharged and supplies a static scope disclosure plus an HTTP response, without checking search or record availability. Consult Documentation for filters and the Guide for interpreting your bounded comparison.