Trendyol API for product, review and search data

Trendyol publishes a seller API, but it's built for merchants to manage their own store — listing products, updating stock and processing orders in their own account. It doesn't let you read another seller's product details, pull a competitor's reviews, or query search rankings for a keyword across the whole marketplace.

The Roketfy Data Engine covers that gap. It reads the same public storefront pages a shopper sees — product pages, review lists, Q&A threads, category and search listings, seller stores — and returns them as structured JSON, for any listing on Trendyol, not just your own store. It's the right tool when you need marketplace-wide visibility rather than order management for a single seller account.

Call `/v1/trendyol/product-detail` with either a full product URL or a `contentId` — the numeric id Trendyol sellers know as the product SKU. The response includes attributes, variants, current ratings, the buybox winner and every other seller listed on that product with their own price and stock, so you can see the full competitive picture on a single listing in one request.

If you already track products by contentId internally, pass that directly and skip URL parsing on your side. An optional `merchantId` lets you scope the same product page to one specific seller when a listing carries several.

Reviews and buyer questions are paginated: `/v1/trendyol/reviews` and `/v1/trendyol/questions` both accept `page` and `pageSize`, and both are marked as batchable endpoints. That means instead of looping page requests yourself, you can submit a batch task through `POST /v1/tasks` and poll for a completed result — the Data Engine handles pagination and retries for you, at the same per-page credit cost as calling the endpoint directly.

Reviews support extra filters worth knowing about: `orderBy` sorts by Trendyol's own helpfulness score, by newest, or by star rating; `hasMediaFiles` keeps only reviews with a photo or video; `tag`, `heightTags` and `weightTags` filter by the aspect tags and reviewer body-size bands that Trendyol generates per product — read page 0 first to see which tags exist for that specific listing before filtering by them.

`/v1/trendyol/search` returns results for a search term in the exact order the storefront shows them, including page position, price, rating, seller and whether a row is a paid placement rather than an organic result — useful for tracking share of voice for a keyword over time. `/v1/trendyol/category-products` returns the same shape for a category page instead of a search term, and `/v1/trendyol/top-rankings` exposes Trendyol's own leaderboards (best seller, most viewed, most favourited, most rated) for a given category id.

All three accept the same sort and filter parameters as the storefront itself — brand ids, leaf category ids, minimum rating, free shipping — so you can reproduce exactly the view a shopper would see, or narrow a broad category down to a specific segment.

Every endpoint listed above costs 1 credit per successful call, including each page of a paginated reviews or questions request. Failed upstream fetches are never billed — you only pay when Trendyol actually returns data. Credits come from one-time packages rather than a subscription, so usage that varies month to month doesn't lock you into a recurring plan.

Authentication is a single Bearer token from your Roketfy dashboard, used on every request and on the equivalent MCP tools, so the same credentials work whether you're calling the REST API from your own backend or wiring it into an AI agent.

Yes. Every endpoint above is also exposed as an MCP tool — `trendyol_product_detail`, `trendyol_reviews`, `trendyol_search` and the rest — so agents built on Claude, Cursor or any other MCP-compatible client can look up Trendyol data directly inside a conversation, using the same API token and the same credit balance as your REST integration.