ForHosting KIT · Text & AI

Reply to reviews

Every unanswered review sits there in public, and a generic 'thank you for your feedback' answers it in the least convincing way possible. This endpoint reads the actual review — praise, complaint, or something mixed — and drafts a reply that responds to what was actually said.

● StablePer request + per review$0.003

Run — $0.003 + $0.0135/review How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

The reply gap on review platforms

Businesses with a hundred locations or a few thousand product listings accumulate reviews faster than any small team can answer them individually, so replies either stop happening or start looking copy-pasted, and shoppers notice both. A reply that ignores the specific complaint — replying about slow shipping to a review about a broken part — reads as worse than silence, because it signals nobody actually read the review. text.review_reply is built to respond to the specific thing a reviewer said, not to a category of review.

What the endpoint does with a review

POST /text/review-reply with the review text and a task_id comes back immediately; the drafted reply arrives by signed webhook or a signed link valid for 24 hours once the async job finishes. The draft matches tone to content — an apology and a concrete next step for a legitimate complaint, warm specificity for praise — rather than reusing one template regardless of star rating.

Why public replies carry weight

A review reply is read by far more people than the original poster; it's read by every future shopper deciding whether a business is worth the risk, which is why review platforms surfaced public responses as a feature in the first place, not an afterthought. A thoughtful reply to a one-star review, visible to everyone who reads that review afterward, does more reputational work than ten replies to five-star reviews that needed no response at all.

Fitting it into a review workflow

Most teams pull this endpoint into whatever tool already aggregates reviews across platforms, so a draft is waiting the moment a new review lands rather than requiring someone to hunt for it. A person still approves before it posts, since a negative review sometimes needs an offline resolution mentioned by name rather than a generic promise, and a screenshot of a genuine defect deserves an answer that names the fix directly, not a vague template. Priced per request plus per review, cost tracks review volume directly and a failed task is never billed.

What you can do with it

Multi-location businesses answering at scale

A restaurant chain drafts a reply for every new location review so none sit unanswered for weeks while a regional manager gets to them.

E-commerce sellers with high review volume

A marketplace seller drafts replies to hundreds of product reviews weekly, catching legitimate complaints early instead of letting them go unaddressed.

Turning a complaint into a visible recovery

A hotel drafts a specific, apologetic reply to a detailed negative review so future guests see the issue was acknowledged and addressed.

Consistent voice across a support and marketing team

A company routes review replies through the endpoint so the tone stays consistent whether marketing or support ends up posting it.

FAQ

How do I generate a reply to a customer review with the API?

POST the review text to /text/review-reply, keep the returned task_id, and collect the drafted reply by webhook or a signed link valid for 24 hours.

Is the review response generator API free?

No, there's no free tier or trial; it costs $0.003 per request plus $0.0135 per review, and a failed task is never charged.

Does it handle negative reviews differently from positive ones?

Yes, the draft's tone matches the content of the review, so a legitimate complaint gets an apology and a concrete next step rather than a generic thank-you.

Can it post the reply automatically?

No, it returns a draft; someone reviews and posts it, which matters most for negative reviews that may need details only your team has.

Does it work for reviews in other languages?

It can draft a reply in the same language as the review when that language is supported; check the endpoint reference for current coverage.

Can I run it across a large batch of reviews?

Yes, each review is its own async request, so a backlog of hundreds of reviews is simply a batch of individual requests.

Is this endpoint live yet?

Yes, it's live and accepting requests now.

Is review data kept after the reply is generated?

No, submitted reviews and generated replies are deleted after the retention window and are never used for training.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/text/review-reply

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/text/review-reply \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"input":"…"}'

const res = await fetch("https://api.kit.forhosting.com/text/review-reply", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "input": "…"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/text/review-reply",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "input": "…"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/text/review-reply", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"input":"…"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/text/review-reply", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "input": "…"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "text.review_reply",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.003

Per review$0.0135

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

max_tokens 20000

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.
`422`	`task_failed`	The task failed after 3 retries. You are never charged for it.

Read the full KIT documentation →