Trendyol, Hepsiburada and n11 data from one API
Turkish price comparison needs all three, and the same product routinely sits at three different prices with three different sellers. One key covers them, and all three expose the seller and the offer stack rather than only the featured price.
All three run merchant APIs that require an approved seller account and return that seller's own catalogue. For reading market-wide prices they do not apply.
Coverage
What the three engines give you
- Trendyol
- search, product/detail, product/offers, product/variants, product/reviews, product/questions, product/coupons
- Hepsiburada
- search, product/detail, product/offers, product/reviews, category, seller
- n11
- search, product/detail, product/reviews, category, seller, resolve
- All three
- the offer stack behind a listing, not just the featured seller
Worked example
Price one product across all three
Search each, then read the offer stack; the featured offer is not always the cheapest.
- 1
POST /trendyol/v1/searchfind it on Trendyol
- 2
POST /trendyol/v1/product/offersevery seller on that listing
- 3
POST /hepsiburada/v1/product/offersthe same product's offer stack
- 4
POST /n11/v1/resolveresolve the n11 listing, then read its detail
Three marketplaces, every seller behind each listing, for one product.
Before you join them
Where the three sources genuinely differ
| trendyol | hepsiburada / n11 | |
|---|---|---|
| Depth | Trendyol is the deepest at 16 actions, including questions and coupons | Hepsiburada and n11 sit at 6 each |
| Variants | Trendyol exposes variants as their own endpoint | the others fold them into detail |
| Resolve | n11 has a resolve step for turning a url into an id | the others take ids directly |
| Stability | Trendyol detail is IP-sensitive and can answer not-found for a live product on a retry | stated here rather than discovered in production |