Reviewflowz API Get an API key

Reply to reviews from your own tool

You end up with every new review in your own tool, a reply drafted for it by the AI reply agent, and a person approving it before it goes live on the platform.

Run calls

Sign in to run every call on this page on your account's data. No key needed.

Before you start

  • A key with replies:write, reviews:read and webhooks: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"]}'
Edit the request

POST /v3/webhook-endpoints in the reference

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_..."
Edit the request

GET /v3/reviews in the reference

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_..."
Edit the request

POST /v3/reviews/{review_id}/reply/draft in the reference

Example answer
{"id": "rpl_7","review": "rev_918273","origin": "reviewflowz","status": "draft","text": "Thank you, Maya! We're glad the summit tickets saved you the queue. See you next time.","author": {"type": "user","name": "Sofia Martin"},"via": "reviewflowz","published_at": null,"editable": true,"deletable": true,"created_at": "2026-11-10T09:05:12Z","updated_at": "2026-11-10T09:05:12Z"}​

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."}'
Edit the request

PATCH /v3/replies/{id} in the reference

Example answer
{"id": "rpl_7","review": "rev_918273","origin": "reviewflowz","status": "draft","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.","author": {"type": "user","name": "Sofia Martin"},"via": "reviewflowz","published_at": null,"editable": true,"deletable": true,"created_at": "2026-11-10T09:05:12Z","updated_at": "2026-11-10T09:20:41Z"}​

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."}'
Edit the request

POST /v3/reviews/{review_id}/reply in the reference

Example answer
{"id": "rpl_7","review": "rev_918273","origin": "reviewflowz","status": "published","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.","author": {"type": "user","name": "Sofia Martin"},"via": "reviewflowz","published_at": "2026-11-10T09:30:00Z","editable": true,"deletable": false,"created_at": "2026-11-10T09:05:12Z","updated_at": "2026-11-10T09:30:00Z"}​

status: published means the reply is live on the platform.

When it can't be posted, the answer says what to do:

  • 409 not_repliable: we can't post to this platform for this source. Send the same call with "publish": false to keep it as a draft, then post it on the platform yourself. The platforms index shows where replies post.
  • 422 reply_too_long: the reply is longer than the platform allows. Shorten it and send it again.
  • 502 publish_failed: the platform didn't take it. detail says why and what to do, like reconnecting the account in the app.
  • 403 trial_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.stage is publish when the platform refused it, or generation when a draft couldn't be written. When data.was_live is true, 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.