Reddit App API · 06 / APP
Service scope and conditions of use
Read the historical archive scope, credential responsibilities, request-credit model and invoice conditions for Reddit App API.
An independent historical retrieval service
Reddit App API is independent of Reddit and is not sponsored or endorsed by Reddit. It provides historical archive retrieval, not a live Reddit feed. It does not supply posting, voting, private messages or Reddit OAuth. App screens and hiking examples on this site are illustrative proposals, not verified search results or operational performance evidence.
The service does not guarantee completeness, current accuracy, permanent availability or retention of archived records, or a service-level commitment. Historical discussion is not current trail, weather or safety guidance. Use retrieved material in accordance with applicable law and third-party rights; access through an API is not a statement that every downstream use is permitted.
Protect domain-specific access
Your API key authenticates retrieval requests and can consume your account’s credits. Keep it on your backend and protect the account password separately. Signup and password-confirmed regeneration display a new full key once; regeneration immediately invalidates the earlier key. No automatic email key delivery or password-reset flow is provided.
Account access on this site uses its own session mechanism. Accounts, API keys and balances are specific to the domain and do not provide access across the other network brands. Review stored backend secrets after a key change and do not put the service credential into a shipped client.
Successful requests and paid credits
One successful retrieval request costs one credit, including an empty result. The number of records in that response does not multiply the charge. $1 corresponds to 1,000 successful retrievals; a minimum $50 top-up provides 50,000 paid credits. There is no subscription, and paid credits do not expire. Any 100-credit trial is conditional on network-wide anti-abuse eligibility and is separate from paid credits.
Requests rejected before reservation do not debit a retrieval credit. Failed upstream requests release the reservation; reconciliation may remain pending if that refund cannot complete immediately. /v1/status is uncharged and is only a static scope/HTTP-response check. An app that loses a response should not assume the underlying request was unsuccessful or uncharged.
Use the current invoice instructions
Create an invoice after signing in and before sending a transfer. Supported assets are USDT on TRON TRC20 and USDC on Ethereum mainnet ERC20. Follow the invoice’s exact recipient, amount, token, network and expiry. Invoice uniqueness does not establish a newly generated receiving address.
Submit the transfer’s transaction hash for verification. Only a confirmed eligible transfer accepted by the server adds credits; a pending status does not. No fixed settlement time or recovery of a wrong-token or wrong-network transfer is promised. The displayed invoice and its actual status govern the payment steps, not hypothetical example screens.
Read the limits with the data
Retrieval returns flat records in archive document order, not globally ranked or chronologically sorted results. Requests allow at most 100 records and 100 pages. Pagination can report an exact count, a lower bound or an unknown total; exhausting a page window does not establish complete coverage. Available parent identifiers do not guarantee a complete discussion.
The retrieval API provides no bookmark, posting or deletion action. A reading list built into your app is your app’s feature and needs its own handling of missing or outdated references. Privacy explains account and payment data practices; those practices do not promise permanent availability of archive content.
