SSENSE Product Data
Prices, variants, availability, and images from ssense.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- ssense.com
- Segment
- Luxury marketplace & e-tail
- Origin
- Canada — founded 2003 in Montreal
- Categories
- Luxury womenswear, Menswear, Streetwear, Shoes
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What SSENSE sells, and how its catalogue behaves
SSENSE is the Montreal retailer that merged luxury and streetwear into one credible assortment before most of the industry accepted the two belonged together. Its buy is younger and more design-forward than traditional luxury e-tail, and its editorial voice drives real demand for the brands it backs.
why teams track it
Why SSENSE data is worth having
SSENSE is where emerging designers get validated, so its assortment functions as a leading indicator for which labels are about to matter. For anyone tracking the luxury-streetwear intersection it is the single most informative source in the market.
Visit ssense.comcollection method
How we collect SSENSE
SSENSE is collected through SSENSE's JSON product endpoints, read per category so the assortment is enumerated completely. 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 ssense.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 SSENSE 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 SSENSE
- Designer attribution across an unusually wide brand roster
- Coverage of emerging labels absent from traditional luxury e-tail
- Both womenswear and menswear on one schema
- Markdown timing across seasonal sale windows
related sources
Tracked alongside SSENSE
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.
