Before you start
- A key with
replies:write,reviews:readandwebhooks:write. Replies post for real: draft (step 2) and approve (step 3) before you post. - The API is part of the Premium plan (see pricing). API-only plans start at $300 a month: book a 30-minute call for a custom quote. Replying is part of the Pro plan, which Premium includes.
- Replies post to these platforms, once the account behind the page is connected in the app, under Integrations → Review Replies:
- Google Maps: Google Business Profile
- Facebook: Facebook Page
- Trustpilot: Trustpilot business account
- App Store: App Store Connect
- Play Store: Google Play Console
- The reviews you answer come from sources you added: steps 1 and 2 of Find and monitor reviews for any business.
The example follows one business, the Eiffel Tower in Paris, answering its Google Maps reviews.
1. Hear about a new review
Subscribe your server to new reviews and to the reply events of step 5:
curl https://api.reviewflowz.com/v3/webhook-endpoints \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-d '{"url": "https://hooks.yourcompany.com/reviewflowz","events": ["review.created", "reply.published", "reply.updated", "reply.failed"]}'
const res = await fetch("https://api.reviewflowz.com/v3/webhook-endpoints", {method: "POST",headers: {"Authorization": "Bearer rfz_live_...","Content-Type": "application/json",},body: JSON.stringify({"url": "https://hooks.yourcompany.com/reviewflowz", "events": ["review.created", "reply.published", "reply.updated", "reply.failed"]}),});console.log(await res.json());
import requestsres = requests.post("https://api.reviewflowz.com/v3/webhook-endpoints",headers={"Authorization": "Bearer rfz_live_...","Content-Type": "application/json",},json={"url": "https://hooks.yourcompany.com/reviewflowz", "events": ["review.created", "reply.published", "reply.updated", "reply.failed"]},)print(res.json())
Edit the request
Each new review then arrives like this (review.created):
{"id": "evt_4821","type": "review.created","timestamp": "2026-11-10T08:40:09Z","data": {"object": {"id": "rev_918273","source": "src_4812","platform": "google_maps","rating": 5,"text": "Booked the summit tickets online and skipped the whole queue. The view at sunset was worth every euro, and the staff on the second floor were patient with our kids.","reviewer": {"name": "Maya Chen","company": null,"avatar_url": null},"date": "2026-11-09T18:32:00Z","reply": null},"source": "src_4812"}}
Keep the review's id (rev_918273 here). No server? Ask for the reviews with no reply that changed since your last check:
curl "https://api.reviewflowz.com/v3/reviews?has_reply=false&updated_after=2026-11-01T00%3A00%3A00Z" \-H "Authorization: Bearer rfz_live_..."
const res = await fetch("https://api.reviewflowz.com/v3/reviews?has_reply=false&updated_after=2026-11-01T00%3A00%3A00Z", {method: "GET",headers: {"Authorization": "Bearer rfz_live_...",},});console.log(await res.json());
import requestsres = requests.get("https://api.reviewflowz.com/v3/reviews",headers={"Authorization": "Bearer rfz_live_...",},params={"has_reply": "false", "updated_after": "2026-11-01T00:00:00Z"},)print(res.json())
Edit the request
- source · Comma-separated source ids.
- platform · Comma-separated platform ids.
- rating · Star ratings, comma-separated: rating=1,2 (4 includes 4.5).
- date_after · Posted on the platform at or after.
- limit · Rows per page (default 50).
- cursor · The next_cursor from the previous page. Leave it out for the first...
- id · Comma-separated review ids: id=rev_1 reads one review.
- location · Comma-separated location ids.
- product · Comma-separated product ids (accounts that group sources into...
- dimension[key] · Reviews of sources with this custom dimension value...
- rating_min · Scores of at least this: rating_min=4.
- rating_max · Scores of at most this: rating_max=3 (3.5 is out).
- date_before
- created_after · Found by Reviewflowz at or after.
- created_before
- source_created_after · Reviews of sources added at or after (bulk imports).
- tag · Comma-separated tag ids.
- owner · Comma-separated owner ids (confirmed assignments).
- topic · Comma-separated topic names.
- subtopic · Comma-separated subtopic names. With topic or sentiment, the same...
- sentiment · With topic, a mention of that topic with that sentiment.
- removed
- language · Comma-separated ISO 639-1 codes.
- country · The reviewer's country, where the platform gives one:...
- q · Full-text search (title, text, pros, cons, reviewer); every word...
- keywords · Like q, but any of the words: keywords=refund,late.
- has_text · Reviews with written text (true) or a rating alone (false).
- text_length_min · At least this many characters of text.
- versions · latest lists only the current version of an edited review; all...
- include · Any of media, reply, events, comma-separated.
- fields · Only these top-level fields (id always comes).
- columns · Comma-separated export columns (rating, date, reviewer,...
- sort · created: newest found first. date: newest posted on the platform...
2. Draft a reply
The account's reply agent writes a draft. Nothing is posted.
curl -X POST https://api.reviewflowz.com/v3/reviews/rev_918273/reply/draft \-H "Authorization: Bearer rfz_live_..."
const res = await fetch("https://api.reviewflowz.com/v3/reviews/rev_918273/reply/draft", {method: "POST",headers: {"Authorization": "Bearer rfz_live_...",},});console.log(await res.json());
import requestsres = requests.post("https://api.reviewflowz.com/v3/reviews/rev_918273/reply/draft",headers={"Authorization": "Bearer rfz_live_...",},)print(res.json())
Edit the request
POST /v3/reviews/{review_id}/reply/draft in the reference
Example answer
Keep the reply's id (rpl_7 here). The draft is the review's draft in the app too, so your team sees it there.
To get the text without saving a draft, send {"save": false}. The answer is 200 with the review, the text, the agent you sent (or null for the default one) and "saved": false. Nothing is kept, so the app's queue is left as it was. That also works on a review that already has a reply.
Send agent to pick another agent from GET /v3/reply-agents. To change how an agent writes, edit its instructions with PATCH /v3/reply-agents/agt_2.
A review that already has a published reply answers 409 reply_published: edit that reply instead (step 4). If the agent can't write a reply, the answer is 422 generation_failed: try once more. A review with no text may have nothing to answer.
3. Let a person approve it
Show the draft in your tool. When the person edits it, save their text:
curl -X PATCH https://api.reviewflowz.com/v3/replies/rpl_7 \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-d '{"text": "Thank you, Maya! We'\''re glad the summit tickets saved you the queue, and we'\''ll pass your thanks to the team on the second floor."}'
const res = await fetch("https://api.reviewflowz.com/v3/replies/rpl_7", {method: "PATCH",headers: {"Authorization": "Bearer rfz_live_...","Content-Type": "application/json",},body: JSON.stringify({"text": "Thank you, Maya! We're glad the summit tickets saved you the queue, and we'll pass your thanks to the team on the second floor."}),});console.log(await res.json());
import requestsres = requests.patch("https://api.reviewflowz.com/v3/replies/rpl_7",headers={"Authorization": "Bearer rfz_live_...","Content-Type": "application/json",},json={"text": "Thank you, Maya! We're glad the summit tickets saved you the queue, and we'll pass your thanks to the team on the second floor."},)print(res.json())
Edit the request
PATCH /v3/replies/{id} in the reference
Example answer
The reply is still a draft. Nothing is posted until step 4.
4. Post it
Send the approved text. The Idempotency-Key makes a retry safe: the reply is posted once.
curl https://api.reviewflowz.com/v3/reviews/rev_918273/reply \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-H "Idempotency-Key: rev_918273-reply-1" \-d '{"text": "Thank you, Maya! We'\''re glad the summit tickets saved you the queue, and we'\''ll pass your thanks to the team on the second floor."}'
const res = await fetch("https://api.reviewflowz.com/v3/reviews/rev_918273/reply", {method: "POST",headers: {"Authorization": "Bearer rfz_live_...","Content-Type": "application/json","Idempotency-Key": "rev_918273-reply-1",},body: JSON.stringify({"text": "Thank you, Maya! We're glad the summit tickets saved you the queue, and we'll pass your thanks to the team on the second floor."}),});console.log(await res.json());
import requestsres = requests.post("https://api.reviewflowz.com/v3/reviews/rev_918273/reply",headers={"Authorization": "Bearer rfz_live_...","Content-Type": "application/json","Idempotency-Key": "rev_918273-reply-1",},json={"text": "Thank you, Maya! We're glad the summit tickets saved you the queue, and we'll pass your thanks to the team on the second floor."},)print(res.json())
Edit the request
POST /v3/reviews/{review_id}/reply in the reference
Example answer
status: published means the reply is live on the platform.
When it can't be posted, the answer says what to do:
409not_repliable: we can't post to this platform for this source. Send the same call with"publish": falseto keep it as a draft, then post it on the platform yourself. The platforms index shows where replies post.422reply_too_long: the reply is longer than the platform allows. Shorten it and send it again.502publish_failed: the platform didn't take it.detailsays why and what to do, like reconnecting the account in the app.403trial_reply_limit: the free trial's 20 replies are used. Subscribe in the app to keep replying.
To change a live reply later, send the new text with PATCH /v3/replies/rpl_7. It's posted again where the platform allows edits, and reply.updated follows.
5. Close the loop
The events subscribed in step 1 tell your tool how each reply ended:
reply.published: the reply is live. Its object is the reply, as step 4 shows it.reply.failed: the reply didn't go out.data.stageispublishwhen the platform refused it, orgenerationwhen a draft couldn't be written. Whendata.was_liveistrue, an edit failed and the earlier reply is still live.
Add reply.drafted to hear about drafts written in the app too. GET /v3/replies?status=draft lists the drafts waiting for approval.
What it costs and where it stops
- Replies post only to the platforms above, once their account is connected in the app.
- A free trial posts up to 20 replies.
- Some platforms cap a reply's length (step 4).
- Rate limits.
When something else fits better
If your team doesn't need its own screen, answer from the Replies page in the app. Its reply rules can answer automatically with the AI agent, or queue reviews for your team.