/trendyol/sellers

POST /api/trendyol/sellers

Price: 5 credits

Get a Trendyol seller (store) by seller id or store URL: name, alias, official_name, city, rating, product count, verified status, store logo and cover image, and seller performance metrics (average shipping time, question response time, product and seller review scores).

How to use it

Fetch a single Trendyol seller (marketplace store) by numeric seller id or a store URL (/magaza/{slug}-m-{sellerId}). Returns one item with name, alias (URL slug), official_name (legal entity), city, rating (0-10 seller score), sell_item_count (number of products in the store), is_verified, has_corporate_invoice, image (store logo) and cover (store banner), plus metrics: activation_age (time on Trendyol), delivery_time (average shipping time), response_time (average question response time) and product_review_score.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — Trendyol seller id or a store URL containing it (examples: "992531", "https://www.trendyol.com/magaza/yenilegelsin-m-992531"; minLength: 1)

Response

• @type string (default: "TrendyolSellerStore")
• id string required
• name string nullable
• alias string nullable
• official_name string nullable
• city string nullable
• url string nullable
• rating number nullable
• sell_item_count integer nullable
• is_verified boolean nullable
• has_corporate_invoice boolean nullable
• image string nullable
• cover string nullable
• metrics object nullable
  • @type string (default: "TrendyolSellerMetrics")
  • activation_age string nullable
  • delivery_time string nullable
  • response_time string nullable
  • product_review_score number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Seller not found (well-formed but nonexistent seller id, or page has no seller data) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.