Dunst Studio Product Data
Prices, variants, availability, and images from dunststudio.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- dunststudio.com
- Segment
- Contemporary & direct-to-consumer
- Origin
- South Korea — Seoul
- Categories
- Unisex, Outerwear, Womenswear, Menswear
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What Dunst Studio sells, and how its catalogue behaves
Dunst is a Seoul label working in oversized, genderless silhouettes, and it sits inside the Korean contemporary scene that has become one of the most influential trend sources in global fashion. Much of the assortment is genuinely unisex rather than duplicated across departments.
why teams track it
Why Dunst Studio data is worth having
Korean contemporary labels now lead rather than follow on silhouette, so tracking them gives you a lead time that Western contemporary brands cannot. Dunst is also a useful structural case: a genuinely unisex catalogue breaks the department-split assumption most apparel data models are built on.
Visit dunststudio.comcollection method
How we collect Dunst Studio
Dunst Studio is collected through Dunst's internal product listing endpoint, which returns the catalogue as structured records rather than rendered markup. Every source gets a dedicated collector rather than a generic crawler, because the field detail that makes this data useful only survives if the extraction is built for the site it runs against.
Structured at the source
Records are read from dunststudio.com's own structured responses wherever they exist, rather than reconstructed from page markup. That keeps the feed stable across visual redesigns.
Validated every run
Each field is checked against expected types and historical ranges. A collector producing anomalies is quarantined and repaired upstream instead of emitting bad prices into your pipeline.
Normalised to one schema
Every brand in the catalogue lands on the same schema, so adding a source is a configuration change on your side rather than another integration to write.
what you get back
Fields in the Dunst Studio feed
A normalised core that is identical across every source, plus the attributes that are specific to this one.
Standard across every source
- Product name, brand, and source URL
- Current price, original price, and currency
- Category and subcategory as the source classifies them
- Colour, size, and variant availability
- Product images, deduplicated across variants
- Description, composition, and care text
- Collection timestamp on every record
Specific to Dunst Studio
- Unisex classification rather than forced department split
- Oversized fit and silhouette attributes from product detail
- Colourway variants with per-colour imagery
- Korean and international pricing where both are exposed
related sources
Tracked alongside Dunst Studio
A single brand is a data point. These are the sources customers most often take with it, all delivered on the same schema.
SOC 2 Type II
Audited controls across security, availability, and confidentiality. Report available under NDA.
GDPR & CCPA
Public catalogue data only. No personal data collected, and a DPA is available on request.
99.9% Uptime SLA
Contractual availability with monitored collectors and a public status page.
Data residency
Choose EU or US processing and storage regions to match your obligations.
questions
Frequently Asked Questions
Everything you need to know before you send us your first request.
Still have questions?
Talk to an engineerReady to Get Started?
Talk to us about your sources and volume. We'll return a sample dataset from your target sites before you commit to anything.
