Vinted and Depop data from one API
Second-hand fashion pricing runs across both, and they behave differently enough that one is not a proxy for the other. Vinted spans twenty European markets from one engine; Depop is where the same item often carries a higher ask.
Neither publishes a public API. Both are app-first marketplaces, which is why resale tooling normally carries its own integration for each.
Coverage
What the two engines give you
- Vinted
- catalog_search, item_detail, seller, seller_items, seller_feedback, brand_search, autocomplete
- Depop
- search, product/detail, product/similar, seller/listings, seller/profile, seller/reviews, suggest
- Markets
- Vinted across 20 European sites from the same engine
- Sellers
- both expose the seller, their listings and their feedback
Worked example
Price one item across both, and across countries
Vinted's country coverage is the part that is hard to replicate by hand.
- 1
POST /vinted/v1/brand_searchresolve the brand to Vinted's own id
- 2
POST /vinted/v1/catalog_searchlistings, repeatable per country site
- 3
POST /depop/v1/searchthe same item on Depop
- 4
POST /depop/v1/product/detailcondition, size and the asking price
One item's resale ask across two platforms and, on the Vinted side, across countries.
Before you join them
Where the two sources genuinely differ
| vinted | depop | |
|---|---|---|
| Geography | 20 European markets in one engine | nine markets |
| Brand lookup | brand_search resolves to a real brand id | brand is a search term |
| Similar items | not exposed | product/similar |
| Feedback | seller_feedback | seller/reviews |