Shopify Junip Reviews Scraper API

Pull public Junip product reviews and site reviews from Shopify stores into one clean spreadsheet. Collect a product's full public review group, monitor the reputation of a store, mine 1-star feedback, or build a review dataset ready to filter, analyze, and export.

🎬 What it does

Paste a Shopify store URL or a product URL. Get back public Junip reviews in structured rows.

Two kinds of input:

1. Store URL returns public Junip site reviews about the store itself. Good for reputation monitoring, service-quality analysis, and recurring brand reports.
2. Product URL returns the product-group reviews shown by that product's Junip widget. Good for quote pulls, product research, launch analysis, and review-history exports.

Shape the results before you pay for them:

• Free filters and sorts: keep any mix of 1 to 5 stars. Sort by newest, oldest, highest rating, lowest rating, most helpful, or featured first.
• Paid keyword search: pull only reviews mentioning a phrase such as "refund", "sizing", or "gift".
• Paid verified, recommendation, media, and reply filters: verified buyers only, recommended reviews only, photos only, videos only, either type of media, or reviews the store publicly replied to.
• Paid date, length, and language filters: narrow to a date window, require a minimum amount of written text, or keep only selected public Junip locales.
• Paid enrichments: translate review titles and text, and archive customer photos or videos to your run storage.

Equivalent URL variants collapse automatically. A store target and a product target remain separate because they return different kinds of Junip reviews. Explanatory status rows are always free.

Good for: Shopify founders watching brand and product feedback, CMOs auditing a launch or competitor, agencies preparing recurring client reports, researchers studying verified buyer sentiment, and analysts building review datasets they can trust.

📋 How to use it

Step 1: Paste your inputs

Drop any combination into Store or product URLs, one per line. Duplicate versions of the same target are cleaned up automatically.

• Store URL: https://woashoes.com/
• Product URL: https://hexclad.com/products/damascus-steel-starter-knife-set-2-pc-espresso

Minimum input, run as-is:

{
  "startUrls": [
    "https://hexclad.com/products/damascus-steel-starter-knife-set-2-pc-espresso"
  ],
  "maxResultsPerUrl": 50
}

maxResultsPerUrl is the only result limit you need. The default is 50 and the maximum is 50,000. It caps site reviews for each store URL and product-group reviews for each product URL.

Step 2: Pick filters and add-ons

Free filters and sorts:

• Star rating filter: keep any combination of 1 to 5 stars.
• Sort order: Newest, Oldest, Highest rating, Lowest rating, Most helpful, or Featured first.

Paid add-ons are billed only when they contribute to a delivered result:

• Keyword search: only reviews whose title or text contains your phrase.
• Verified only: only reviews Junip marks as verified purchases.
• Media filters: only reviews with a photo, only with a video, or only with either.
• Store-reply only: only reviews the merchant has publicly replied to.
• Recommended only: only reviews whose author recommends the product or store.
• Date range: only reviews posted between two inclusive dates.
• Minimum text length: require a written review body of at least the selected length.
• Language filter: only reviews with the Junip locale codes you select.
• Translation: translate review titles and text into your chosen language, billed only when translated text is returned.
• Media archiving: save up to 10 photos or videos per product review with a 3 MB limit per file, billed only per file stored.

Use the Output fields section to turn off optional columns you do not need. Core status, row type, product and review IDs, rating, text, scrape time, and error fields remain available for reliable downstream processing.

Step 3: Run it and get your results

Click Start. Rows stream into the Output tab as they arrive. The dataset includes four ready-made views:

• Overview: the most useful columns across product reviews, site reviews, and explanatory rows.
• Product reviews: product-group review details, reviewer signals, replies, votes, media, and exact per-row product identity.
• Site reviews: public store-review details, reviewer signals, replies, votes, locale, and store identity.
• Language & Media: public locale, survey answers, translated text, source media, and archived file references.

Every row includes a status and rowType. status: "Success" means the row contains a public review. rowType is review for product-group reviews, store_review for site reviews, or status for an explanation. Explanatory rows include a stable error code such as invalid_url, junip_not_detected, product_unavailable, or no_matching_reviews, and are never charged as Review events.

Download the dataset as JSON, CSV, or Excel from Storage, or read it directly through the Apify API.

💰 Pricing

Pay only for results and optional enhancements you actually receive. No subscription and no minimum spend.

Event	Price	When
Actor Start	$0.05 per 1,000 starts	per Actor start, with one event per GB of memory and a minimum of one
Review	$1.50 per 1,000 rows	per product review or site review delivered
Add-on: Advanced filter	$0.50 per 1,000 rows	per delivered review kept by one or more paid filters
Add-on: Review translated	$2.00 per 1,000 rows	per delivered review for which translated text is returned
Add-on: Media downloaded	$1.00 per 1,000 files	per review photo or video archived successfully

Rating filters, all six Junip sorts, public locale values, source photo and video URLs, standard output fields, and status rows are free.

💡 Good to know

• Store URLs return site reviews only. Submit product URLs when you need product reviews. A store can have many product reviews but few or no public site reviews.
• Product groups follow the public widget. Junip can show reviews attached to related products in one product review group. The productId, productHandle, productTitle, and productUrl fields identify the exact product attached to each returned row.
• Dedup is automatic. Locale prefixes, www variants, trailing slashes, query strings, hash fragments, and case variations of the same product handle are fetched once.
• Not on Junip? If a store runs Okendo, Loox, Yotpo, or Judge.me instead, the uncharged status row names the detected provider and links to the matching sibling Actor.
• Status rows are never charged. Unsupported providers, unavailable products, empty filtered results, and rejected URLs return a stable error value that explains the outcome.
• Field coverage matches the public source. If Junip did not publish a requested value, the field returns null. Fields turned off in the Output fields section are omitted.
• Site-review media is not exposed by this source. Product reviews can include customer photo and video URLs and optional archived files.
• Media limits are strict. Up to 10 files per product review and 3 MB per file. Only verified photo or video responses are stored successfully and billed.
• Runs are independent. No cross-run history is kept. Schedule runs and compare reviewId values on your side to track new reviews.
• Files and datasets live in your Apify storage. Retention depends on the Apify plan of the account running the Actor.

❓ FAQ

Do I need a Junip or Shopify account? No. The Actor reads only publicly published storefront and review data.

What if a store does not use Junip? You get one uncharged status row that explains the outcome. When the Actor recognizes a supported sibling widget, it names and links the matching Okendo, Loox, Yotpo, or Judge.me scraper.

Why did a store URL return fewer reviews than expected? Store URLs return Junip site reviews, not the store's product-review catalog. Submit individual product URLs to collect product reviews.

Why does a product URL return reviews for related products? Some merchants combine related products in one Junip review group. The Actor matches the public widget and includes the exact product identity on every review row.

What if no reviews match? You get an uncharged status row with error: "no_matching_reviews". It may mean the target has no public reviews or that the selected filters removed every review.

Why are some fields null? Not every public review includes every value. For example, older reviews may not include a locale, survey answers, an edit time, or a recommendation response. null means the field was requested but Junip did not expose a value.

Can I schedule this? Yes. Use Apify Schedules to run on any cadence and compare reviewId across snapshots to track new reviews.

Can I export to Excel or Google Sheets? Yes. Open the run's Storage tab and choose CSV, Excel, JSON, or another supported format.

Which stores work? Shopify stores with a publicly reachable Junip review widget. Product URLs need a readable product review group; store URLs need publicly published site reviews.

How long are my results stored? Results live in your Apify dataset and downloaded media lives in the run's key-value store. Retention depends on your Apify plan.

🔗 Other tools you might like

• Shopify Okendo Reviews Scraper API: reviews and product data from Shopify stores using Okendo.
• Shopify Loox Reviews Scraper API: reviews and product data from Shopify stores using Loox.
• Shopify Yotpo Reviews Scraper API: reviews and product data from Shopify stores using Yotpo.
• Shopify Judge.me Reviews Scraper API: reviews and product data from Shopify stores using Judge.me.

⚖️ Disclaimer

This tool is intended for personal, research, and educational use. You are responsible for complying with Shopify's and Junip's Terms of Service and any laws that apply in your jurisdiction. The developer is not liable for misuse. Data availability depends on the storefront's public configuration at run time.

Keywords: shopify reviews, junip reviews, shopify review scraper, junip review scraper, product reviews export, shopify site reviews, review dataset, review sentiment data, verified buyer reviews, ecommerce review data