Getting started

SubReply API

The public SubReply API exposes the product's Reddit social selling engine, without going through the dashboard.

Scrape — you give it subreddits and keywords, the API hands back recent posts, scored by relevance and by buying intent.
Generate — you give it a post and your product, the API writes a natural comment in the language of the thread, designed not to trigger a shadowban.
Publish — you give it a comment, the API posts it on Reddit from a SubReply-managed account, behind a residential proxy.

Base URL

Every endpoint is a POST, accepts and returns application/json, and lives under a single base:

Base URL

https://subreply.io/api/v1

There is no v2 in the works and no field that will vanish without notice: what this page describes is the contract.

First call in 30 seconds

Generate a key on your API keys page, then paste this into a terminal. Scanning costs no credits: run it as many times as you need to dial in your keywords.

cURL

curl -s -X POST https://subreply.io/api/v1/scrape \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer sr_live_VOTRE_CLE_API" \
  -d '{
    "subreddits": ["r/entrepreneur"],
    "keywords": ["trouver des clients"],
    "target_language": "fr",
    "limit": 3
  }'

Use cases

The API is stateless: nothing is stored on the SubReply side, neither the scraped posts nor the generated comments. You keep the data, and you plug the API in wherever you want.

n8n, Zapier and Make

One HTTP Request node is enough: three chained POST calls make a complete Reddit prospecting workflow, without writing a line of code.

Python or Node.js scripts

JSON in, JSON out. No SDK to install and no pagination to handle: one fetch and you have your scored posts.

CRMs and sales tools

Push the posts flagged as leads into your CRM along with their score, their customer intent and their Reddit permalink.

AI agents

Hand these three endpoints to an LLM and it prospects on its own: it searches, it writes, it publishes. This page is written to be read by an agent as much as by a human.

What each action costs

The model is simple: searching is free, only production is billed. So you never pay for a scan that finds nothing.

Action	Endpoint	Credits
Scrape posts	`POST /api/v1/scrape`	0
Generate a comment	`POST /api/v1/generate-comment`	35
Publish a comment	`POST /api/v1/publish`	50

Scanning is free, but not open to everyone

A scan debits nothing, but it does require a balance of at least 35 credits — the price of one comment. Otherwise the endpoint answers 402: scraping for an account that cannot produce anything afterwards helps no one.

Limits and behaviours to know about

No rate limit today. Your credit balance is the only ceiling. If a quota ever appears, it will be announced here before it is enforced.
Publishing is slow — up to two minutes: a real browser opens the post and types the comment. Set your HTTP client timeout to at least 180 s (in n8n: Options → Timeout).
Charges are idempotent per post : replaying a call on the same Reddit URL after a network timeout does not bill twice. The second call returns credits_used: 0.
An empty scan is a result, not a failure. The freshness, relevance and product-fit filters are strict — zero posts beats ten off-topic ones.

Errors all share the same shape and are detailed on the error codes page.