Reviewflowz API Get an API key

Show reviews on your website

You end up with a reviews page like lugg.com/reviews: your rating on each platform in a band at the top, a wall of 5-star reviews, and two filters above it, "Use case" and "City". Lugg built that page with the Reviewflowz API. The examples below use made-up data.

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 widgets:write for step 1, organize:write for steps 3 and 4, and reviews:read and sources:read for the page itself.
  • Your review pages added as sources: steps 1 and 2 of Find and monitor reviews for any business.
  • 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. Widgets are part of the Pro plan, which Premium includes.

1. The quick way: a widget

If a ready-made layout is enough, a widget shows your reviews with nothing to build on your side.

curl https://api.reviewflowz.com/v3/widgets \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-d '{"name": "Reviews page","template": "masonry","sources": ["src_5101", "src_5102", "src_5201"],"count": 24,"min_rating": 5,"require_content": true,"require_reviewer": true,"tags": ["tag_12"]}'
Edit the request

POST /v3/widgets in the reference

Example answer
{"id": "wdg_7","name": "Reviews page","template": "masonry","sources": ["src_5101","src_5102","src_5201"],"count": 24,"min_rating": 5,"require_content": true,"require_reviewer": true,"tags": ["tag_12"],"embed": {"script": "<script src=\"https://app.reviewflowz.com/iframes/56857a89-d15d-4b63-95d4-0a0c07bcda5d/script.js\" defer type=\"text/javascript\"></script>","iframe": "<iframe src=\"https://app.reviewflowz.com/iframes/56857a89-d15d-4b63-95d4-0a0c07bcda5d\" id=\"rvwflwz-41\" style=\"width: 1px; min-width:100%;\"></iframe>"}}​

Paste embed.script in your page, then embed.iframe where the reviews go. GET /v3/widgets/wdg_7 gives the same code later.

A widget shows its sources' newest reviews by date posted, up to count (1 to 100), rated min_rating or more. tags keeps the reviews with any of those tags, and require_content and require_reviewer keep the ones with text and a reviewer's name. custom_css styles it.

For a layout of your own, like Lugg's, build the page from the API: steps 2 to 7.

2. The ratings band

GET /v3/ratings gives each source's rating and review count, one row per source.

curl "https://api.reviewflowz.com/v3/ratings?source=src_5101,src_5102,src_5201,src_5301,src_5302" \-H "Authorization: Bearer rfz_live_..."
Edit the request

GET /v3/ratings in the reference

Example answer
{"data": [{"source": "src_5101","platform": "google_maps","country": "worldwide","score": 4.9,"count": 1312,"as_of": "2026-11-10"},{"source": "src_5102","platform": "google_maps","country": "worldwide","score": 4.8,"count": 874,"as_of": "2026-11-10"},{"source": "src_5201","platform": "trustpilot","country": "worldwide","score": 4.7,"count": 2210,"as_of": "2026-11-10"},{"source": "src_5301","platform": "app_store","country": "worldwide","score": 4.9,"count": 15620,"as_of": "2026-11-10"},{"source": "src_5302","platform": "play_store","country": "worldwide","score": 4.6,"count": 3048,"as_of": "2026-11-10"}],"next_cursor": null,"has_more": false}​

Shortened: each row also has the change over 7 and 30 days. The app stores also rate per country: country=all lists those rows too. When a platform has several of your pages, like a listing per city here, add their counts and weight each score by its count to show one number for the platform.

3. Tag reviews by use case

Create one tag per use case. With auto_check: true, the tag is applied for you.

curl https://api.reviewflowz.com/v3/tags \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-d '{"name": "Furniture delivery", "auto_check": true}'
Edit the request

POST /v3/tags in the reference

Example answer
{"id": "tag_12","name": "Furniture delivery","auto_check": true,"review_count": 0,"created_at": "2026-11-01T09:00:00Z"}​

Every new review is then read by the AI tagger, which adds the tags with auto_check that it matches. It only sees each tag's name, so name use cases the way your customers say them.

To tag the reviews you already have, open Reports → Tags in the app, click Manage tags, then Tag past reviews.

To tag a review yourself, PUT /v3/reviews/rev_7310021/tags/tag_12 the tag on it. Sending it again changes nothing, and DELETE /v3/reviews/rev_7310021/tags/tag_12 takes it off. The answer lists the review's tags.

curl -X PUT https://api.reviewflowz.com/v3/reviews/rev_7310021/tags/tag_12 \-H "Authorization: Bearer rfz_live_..."
Edit the request

PUT /v3/reviews/{review_id}/tags/{tag_id} in the reference

Reviews also carry topics: what each review talks about (topic Staff, subtopic Friendliness) and with what sentiment. These need sentiment analysis turned on once, in the app under Reports → Sentiment: it builds your topics from the reviews you have, and every new review gets them after that. GET /v3/topics lists them, and GET /v3/reviews filters on topic=, subtopic= and sentiment=positive.

4. Group by city

A city belongs to a source: give each local page its city with a custom dimension.

curl https://api.reviewflowz.com/v3/dimensions \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-d '{"label": "City"}'
Edit the request

POST /v3/dimensions in the reference

Example answer
{"key": "city","label": "City","source_count": 0,"created_at": "2026-11-01T09:00:00Z"}​

Then set it on up to 100 sources per call. A string sets the value, null clears it, and nothing is written unless every row is valid.

curl -X PATCH https://api.reviewflowz.com/v3/sources/dimensions \-H "Authorization: Bearer rfz_live_..." \-H "Content-Type: application/json" \-d '[{"source": "src_5101", "city": "San Francisco"},{"source": "src_5102", "city": "Chicago"}]'
Edit the request

PATCH /v3/sources/dimensions in the reference

The answer lists the sources with their dimensions. A page added later takes its city in the same call that adds it: "dimensions": {"city": "Chicago"} in POST /v3/sources. GET /v3/dimensions/city/values lists the cities for your filter. If your sources already belong to locations in the app, location= filters the same way.

Reviews from a page that covers every city, like an app store's, have no city. Show them when no city is picked.

5. The wall

GET /v3/reviews takes each filter of the page. One at a time:

Parameter Keeps
rating_min=5 5-star reviews
has_text=true Reviews with written text, not a rating alone
text_length_min=80 Reviews with at least 80 characters of text
language=en Reviews in English (ISO 639-1 codes, comma-separated)
tag=tag_12 Reviews with that tag ("Use case"). Several ids: any of them
dimension[city]=Chicago Reviews of sources in Chicago ("City"). Several values: any of them
removed=false Leaves out reviews the platform took down
sort=date Newest posted first, instead of newest found
fields=... Only these fields. id always comes
include=media The reviewer's photos and videos. Name media in fields too

Together, for the Furniture delivery wall in Chicago:

curl -G https://api.reviewflowz.com/v3/reviews \-H "Authorization: Bearer rfz_live_..." \-d tag=tag_12 \-d "dimension[city]=Chicago" \-d rating_min=5 \-d has_text=true \-d text_length_min=80 \-d language=en \-d removed=false \-d sort=date \-d fields=source,rating,text,reviewer,date,tags,media \-d include=media
Edit the request

GET /v3/reviews in the reference

Example answer
{"data": [{"id": "rev_7310021","source": "src_5102","rating": 5.0,"text": "Two movers carried a sectional up four flights without a scratch on the walls. Booked at noon, done by three.","reviewer": {"name": "Dana R.","company": null,"avatar_url": null},"date": "2026-11-08T19:12:00Z","tags": [{"id": "tag_12","name": "Furniture delivery"}],"media": {"photos": [],"videos": []}},{"id": "rev_7298457","source": "src_5102","rating": 5.0,"text": "Bought a dresser on a marketplace and had it at my door the same afternoon. The driver sent photos at pickup.","reviewer": {"name": "Marcus T.","company": null,"avatar_url": null},"date": "2026-11-03T15:47:00Z","tags": [{"id": "tag_12","name": "Furniture delivery"}],"media": {"photos": [],"videos": []}}],"next_cursor": null,"has_more": false}​

Up to 500 reviews a call; next_cursor continues. reviewer.name is the name the platform shows: keep the first word for a first name. The city of each review is its source's dimensions.city, from GET /v3/sources.

6. Serve it from your server

Call the API from your server, never from the visitor's browser: the key would be in the page for anyone to copy. Give the key your server uses read permissions only. Keep the answers on your server and build the page from them, so a visit makes no API call. Step 7 tells you when to update them.

7. Keep it current

Subscribe your server to these events, as in step 4 of Find and monitor reviews:

Back after downtime? GET /v3/reviews?updated_after= with your last check's time lists everything that changed.

What it costs and where it stops

  • Automatic tags go on new reviews. The reviews you already have are tagged from the app (step 3).
  • Topics and sentiment start once sentiment analysis is turned on in the app.
  • A city is set per source, not per review.
  • 500 reviews per call. Rate limits.

When something else fits better

If the widget's layout works for your page, step 1 is the whole job: no server, no code.