Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can store Olive Young and Naver Shopping reviews in one JSON shape, but the sources you collect from matter. Naver’s official Shopping Search API returns product search results in JSON or XML. Its documented fields describe products and listings, not customer review text. Review export for these two sites, as described in a 2026 tutorial, relies on a third-party hosted extraction tool (an Apify Actor), not an official Naver or Olive Young review API. The practical approach is to use one common envelope for every review record, keep each platform’s identifiers and gaps visible, and verify the platform terms and tool pricing before you collect anything.
What Naver’s official Shopping Search API covers
The NAVER Developers Shopping Search API is a documented search service. It returns shopping search results as JSON or XML, and its response describes product listings. The documented fields include a productId, a title, a URL, an image URL, low and high prices, seller, maker, brand, and category. Requests carry client credentials in request headers. The reference page reports a daily limit of 25,000 search API calls; that figure was stated on the NAVER Developers page accessed on 7 October 2026, so check the live page before you plan around it.
What the API does not document is review retrieval or export. Use it to discover products and listing metadata, which can supply the productId and product context for a review record. Do not treat it as a source of review text, ratings, or review dates. The NAVER Developers Shopping Search API reference is the authoritative description of its scope.
The review-export route: a third-party Actor, not an official API
The only documented review-export workflow in the material reviewed is a tutorial published on DEV Community by WebiStudio, dated 28 September 2026, titled “Export Olive Young and Naver Shopping reviews into one JSON schema.” It describes an Apify Actor that returns public Olive Young and Naver Shopping reviews as normalized dataset items. The Actor’s output schema is published on the Apify Actor output-schema page.
#1 Best Overall
Three distinctions matter when you cite or build on this route:
- Who publishes it. The tutorial is publisher-authored. It is useful documentation of a workflow, but it is not an official platform statement and not independent validation of the service’s output.
- What is not established. The sources do not show that Olive Young or Naver offers an official review API, that the platforms authorize this kind of scraping or reuse, or that the Actor will remain available on its current terms.
- Coverage. The Actor’s output depends on what the public pages expose at the time of the run. The tutorial does not claim complete coverage of every review on a product.
One shared record schema
The WebiStudio tutorial uses ten shared fields. They are a practical starting point for a common envelope, not a universal industry standard. You define the types and null conventions in your own schema.
| Field | What it holds | Source handling |
|---|---|---|
| source | Platform the record came from, such as oliveyoung |
Always set; keep it so mixed datasets stay traceable |
| productId | Product identifier on the source platform | Olive Young goods number, or the Naver productId; keep the source’s own format |
| reviewId | Review identifier | Source-specific; treat as opaque and do not assume a shared format across platforms |
| rating | Star rating given by the reviewer | Store the numeric value as the source provides it |
| text | Review body | Stored as provided by the source, without inferred edits |
| date | Review date | Normalize to one format in your schema (the example uses ISO 8601 dates) |
| hasPhoto | Whether the review includes a photo | Boolean |
| photoPaths | Paths or references to review photos | Empty array when there are none |
| isRepurchase | Whether the reviewer marked a repurchase | Use null when the source does not supply the value |
| scrapedAt | When your process collected the record | Generate it in your own pipeline; it is not a platform-supplied value |
Source differences you must preserve
A common envelope can hide real differences between platforms. The tutorial states that Naver review-list results do not include helpful votes or skin profiles. The described export also omits reviewer names, account identifiers, and profile images. Those are not gaps to fill. Do not add a helpfulness field to Naver records by default, do not create placeholder skin-profile values, and do not infer reviewer identity from other data.
- Keep the
sourcefield on every record, and add any platform-specific fields to a separate object rather than widening the shared envelope. - Use
nullfor a value a source does not provide, and an empty array for a list that is empty. Never write the string “unknown” or a guessed number in its place. - Where a count of reviews returned is lower than requested, record the actual count in your run log. The tutorial notes that fewer results may come back when fewer reviews exist or access is restricted.
An illustrative record
The following example shows the envelope with the tutorial’s field names. The values are illustrative. They do not show what either platform guarantees about identifiers, formats, or content.
{
"source": "oliveyoung",
"productId": "A000000223414",
"reviewId": "source-specific-id",
"rating": 5,
"text": "Review text as provided by the source",
"date": "2026-01-15",
"hasPhoto": false,
"photoPaths": [],
"isRepurchase": null,
"scrapedAt": "2026-10-07T09:48:17.418465Z"
}A Naver record uses the same envelope with "source": "naver" and a Naver productId. Its isRepurchase value follows the same rule: null unless the source supplies it.
Running the Actor: inputs and limits
The tutorial describes these input forms:
- Olive Young goods numbers, or Olive Young product URLs
- Naver Smart Store or Naver Brand Store product URLs
- A review cap per run, and a sorting selection
The tutorial’s example input includes a product ID, a review cap, and a sorting option. It also shows a synchronous run endpoint and a charge cap in the example. Confirm the current input names and endpoint in the Actor’s own documentation before you write code against them, since the tutorial is a dated snapshot.
Expect the count of returned reviews to be lower than the cap in some cases. The tutorial attributes this to fewer available reviews or restricted access.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesCost and pricing
The WebiStudio tutorial, dated 2026, states a price of $0.15 per started block of 50 returned reviews per run. That is a vendor-published figure, not an independently verified quote, and it is time-sensitive. Check the Actor’s pricing page before you budget for a run.
The tutorial also notes that splitting one batch into several small runs may increase cost, so plan the number of runs with that in mind. Set the charge cap in your run configuration so a large run cannot exceed your limit unexpectedly.
Terms, privacy, and reuse
The tutorial itself tells readers to check the source site’s terms and the applicable privacy requirements. The material reviewed does not settle those questions for Olive Young or Naver, and this article does not provide legal assurance. Before you collect or reuse review text, read the current terms of each platform, and check the privacy rules that apply to the reviewers and to your jurisdiction. Reviews often contain personal information, so avoid storing reviewer identifiers you do not need and set a retention period in your schema.
Implementation checklist
- Confirm the current terms of Olive Young and Naver for review collection and reuse, and record the date you checked.
- Use the Naver Shopping Search API only for product discovery and listing metadata, and confirm the live quota and credentials for your account.
- Test the Actor on a small product set first, and check the returned count against the review cap.
- Verify the Actor’s current price on its pricing page, and set a charge cap for each run.
- Define your schema with explicit types,
nullfor missing source values, and an empty array for empty lists. - Keep the
sourcefield on every record, and store platform-specific fields separately. - Generate
scrapedAtin your own pipeline, and log the actual number of records returned per run.
The WebiStudio tutorial is at dev.to/webistudio_kr. Read it as one publisher’s description of a workflow, and check each claim against the current source before you rely on it.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
“
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
