Reviewflowz API Get an API key

Keep a warehouse or BI tool in sync

You end up with a table that holds every review of your sources, filled once, then kept current: new reviews added, edits and removals applied, deleted reviews gone.

Run calls

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

Before you start

  • No code needed for a BI tool or a sheet. For Power BI, Excel, Tableau, Qlik Sense, Domo or Looker Studio, create a connection in the app under Integrations → Data Sync: it feeds every review, rating and location to the tool. For a Google Sheet, connect Google Sheets under Integrations → Forward Reviews. The steps below are for your own warehouse.
  • A key with reviews:read, sources:read and webhooks:write.
  • 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.
  • Your review pages added as sources: steps 1 and 2 of Find and monitor reviews for any business.

The example follows the Eiffel Tower's reviews into your warehouse.

1. Copy everything once

Note the time, then page through every review, 500 a call. Pass next_cursor back as cursor until has_more is false. Reviews found while you page don't shift the pages.

curl "https://api.reviewflowz.com/v3/reviews?limit=500" \-H "Authorization: Bearer rfz_live_..."
Edit the request

GET /v3/reviews in the reference

Example answer
{"next_cursor": null,"has_more": false,"data": [{"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.","date": "2026-11-09T18:32:00Z","removed": false,"removed_at": null,"previous_version": null,"root_review": "rev_918273","latest_version": true,"created_at": "2026-11-10T08:40:09Z"}]}​

Shortened: each review also has location, title, pros, cons, language, reviewer, url, tags, owners and topics. Store each review under its root_review, and keep its id beside it. An edited review is a new version with a new id, and every version shares the root_review of the first. This list holds the latest version of each review only. Add versions=all to copy the earlier versions too.

2. Stay current

On your own schedule, ask for everything that changed since the start of your last run:

curl "https://api.reviewflowz.com/v3/reviews?updated_after=2026-11-12T00%3A00%3A00Z&limit=500" \-H "Authorization: Bearer rfz_live_..."
Edit the request

GET /v3/reviews in the reference

The answer has the reviews found, edited, removed, reinstated, replied to, tagged or given an owner since that time, in the shape of step 1, with next_cursor as before. Upsert each one on its root_review. The first time, send the time you noted in step 1. After that, send the time your previous run started, not when it ended: a review found while it ran comes again, and the upsert makes that harmless.

Or have each change sent to you as it happens. Subscribe a URL of yours to the events your table needs:

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", "review.updated", "review.removed", "review.reinstated", "review.deleted", "review.tagged", "review.untagged", "source.deleted"]}'
Edit the request

POST /v3/webhook-endpoints in the reference

Example answer
{"id": "we_12","url": "https://hooks.yourcompany.com/reviewflowz","events": ["review.created","review.updated","review.removed","review.reinstated","review.deleted","review.tagged","review.untagged","source.deleted"],"status": "active","secret": "whsec_MfKQ9r8GKYqrTwjUPD8ILPZIo2LaLaSw"}​

Keep the secret for step 4. Each event's data.object is the review as the API returns it at the moment it's sent: upsert it on its root_review, as in the poll. A source's first import sends no review.created: step 1 covers that history.

Polling or not, subscribe to review.deleted and source.deleted: they are how deleted reviews leave your table. A review.deleted names the review by id ({"id": "rev_...", "deleted": true}): delete the row with that id. A source.deleted names the source: delete every row of that source.

3. Apply edits and removals

Each review carries what you need to apply a change:

Field What to do with it
root_review The row to write. Every version of a review shares it.
previous_version Set on an edit: the id of the version this one replaced. Your row moves to the new id.
latest_version true on the current version. With versions=all, keep only these as current.
removed, removed_at true when the platform took the review down or hid it as not recommended. The review stays in the API: keep the row and flag it.

review.updated brings an edit, review.removed a removal, and review.reinstated sets removed back to false. The poll in step 2 lists the same reviews.

4. Make it safe

  • Check the signature of every event with the secret from step 2. Webhooks shows how, with code.
  • Skip an event you've handled. The same event can arrive twice. Keep each event's id (evt_...) and ignore one you've seen.
  • Answer fast. Return 2xx at once and load the row after.

If your server was down, GET /v3/events lists the events sent, newest first, each with its deliveries. Narrow it with type= and created_after=:

curl "https://api.reviewflowz.com/v3/events?created_after=2026-11-10T00%3A00%3A00Z" \-H "Authorization: Bearer rfz_live_..."
Edit the request

GET /v3/events in the reference

Example answer
{"data": [{"id": "evt_4821","type": "review.created","timestamp": "2026-11-10T08:40:09Z","created_at": "2026-11-10T08:40:10Z"}],"next_cursor": null,"has_more": false}​

Shortened: each event also has its data, with the object as it is now, and its deliveries. A delivery whose status is exhausted never reached you: every try failed. Send it again:

curl https://api.reviewflowz.com/v3/events/evt_4821/redeliver \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-d '{"endpoint": "we_12"}'
Edit the request

POST /v3/events/{id}/redeliver in the reference

Example answer
{"data": [{"id": "dlv_900","endpoint": "we_12","status": "pending","attempt_count": 0}]}​

Leave out endpoint to send it to every active endpoint subscribed to that event. For a long outage, run the poll from step 2 from the time your server went down. Then apply the deletions this list shows with type=review.deleted,source.deleted.

An endpoint that was switched off comes back with PATCH /v3/webhook-endpoints/we_12 and {"status": "active", "replay": true}, which also sends every event it missed.

5. Get the columns of the CSV export

If your warehouse already loads the app's CSV export, ask for the same columns with columns=, or columns=all for every column your account has, custom dimensions included. With fields=id, each review is its id and those columns alone:

curl "https://api.reviewflowz.com/v3/reviews?updated_after=2026-11-12T00%3A00%3A00Z&fields=id&columns=rating,date,reviewer,review_profile,tags,reply_text,last_seen" \-H "Authorization: Bearer rfz_live_..."
Edit the request

GET /v3/reviews in the reference

Example answer
{"data": [{"id": "rev_918273","columns": {"rating": 5.0,"date": "2026-11-09T18:32:00.000Z","reviewer": "Maya Chen","review_profile": "Tour Eiffel","tags": "Tickets","reply_text": "Thank you, Maya! We're glad the summit tickets saved you the queue. See you next time.","last_seen": "2026-11-12T06:10:00.000Z"}}],"next_cursor": null,"has_more": false}​

Each value is the cell a CSV export writes for that review. A column that no source of your account fills comes back null. An unknown key answers 400 invalid_parameter with the list of keys you can use.

What it costs and where it stops