Mytheresa Product Data
Prices, variants, availability, and images from mytheresa.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- mytheresa.com
- Segment
- Luxury marketplace & e-tail
- Origin
- Germany — Munich, online since 2006
- Categories
- Luxury womenswear, Menswear, Shoes, Bags, Kids
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What Mytheresa sells, and how its catalogue behaves
Mytheresa grew out of a single Munich boutique into one of the most disciplined luxury e-tailers in the market, known for a tightly edited assortment and an unusually affluent customer base. It buys its own inventory and carries a narrower, deeper selection than the large marketplaces.
why teams track it
Why Mytheresa data is worth having
Mytheresa is the European counterweight to NET-A-PORTER, and comparing the two shows how differently two expert buyers read the same designer season. Its narrow assortment also means inclusion is itself a signal: a product carried by Mytheresa has passed a stricter filter than one listed on a marketplace.
Visit mytheresa.comcollection method
How we collect Mytheresa
Mytheresa is collected through Mytheresa's internal GraphQL API, which returns exactly the fields requested with stable typing. 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 mytheresa.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 Mytheresa 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 Mytheresa
- GraphQL-sourced fields with stable typing across runs
- Designer attribution separate from product name
- Owned-inventory pricing and markdown timing
- Size availability per product
related sources
Tracked alongside Mytheresa
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.
