Collect Trendyol product data with a single API call
Send a Trendyol URL and receive rendered, parsed data back.
The workflow handles JavaScript execution, proxy rotation, and bot-detection handling so you can focus on prices, stock, and seller signals rather than browser infrastructure.
Decide which Trendyol job you are doing
Three recurring jobs dominate Trendyol collection. First, track what shoppers pay: prices and discount tiers per SKU feed pricing intelligence and promotion monitoring. Second, watch availability: stock state, restock cadence, and inventory swings per SKU support supply-side modelling and merchandising choices. Third, judge sellers: ratings, response rate, and review counts per shop feed seller-quality checks and competitor research. Decide which job you are doing first, because it determines which fields you must capture on every run and how often you need to re-check them.
How it works, step by step
Step 1: Create an account and copy your API key; a trial allowance is available as described in the owner inputs. Step 2: Install the SDK for your stack — Python, Node, Go, PHP, or Ruby — so each scrape is one function call instead of a browser you must run yourself. Step 3: Pass any Trendyol URL plus your key to the endpoint; rendering and bot handling happen server-side and you receive parsed HTML or structured JSON. Step 4: Add advanced parameters only when the page needs them. A practical checklist before your first run: confirm the URL is public, choose HTML or JSON output, decide whether JavaScript rendering is required, and pick a country if content varies by location.
Choose the right output mode
Beyond the core fetch, several output modes fit different downstream work. Natural-language extraction rules or precise CSS selectors return structured JSON for product pages. Full-page screenshots show how a browser actually rendered the page, useful for visual checks. JavaScript scenarios can click, scroll, or wait for dynamic content before capture. Clean Markdown output suits feeding page content into a language model for marketplace analysis. Automation tools such as n8n can drive catalog and price-monitoring workflows without writing scraper code. Match the mode to the decision: JSON for pipelines, screenshots for verification, Markdown for analysis.
Operational notes
The service is positioned for data analysts, growth teams, developers, and e-commerce businesses. It does not collect or store personal data from scraped sites unless a user explicitly requests it. Proxy rotation and headless-browser rendering are used to mimic ordinary browsing and reduce IP-based blocking risk. Capacity scales across many browsers and rotating proxies, with typical results described as arriving within a few seconds even on JavaScript-heavy pages. Treat speed and scale figures as owner-confirmed claims to verify at implementation time.
| Field | What it tells you | Typical use |
|---|---|---|
| SKU | Product identifier | Joining price and stock records |
| Brand | Manufacturer or label | Catalogue grouping |
| Price | Current selling price | Pricing intelligence |
| Discount tier | Promotion level applied | Promo monitoring |
| Stock state | Whether the item is available | Restock and availability checks |
| Seller rating | Shop quality signal | Seller-quality research |
| Review count | Volume of shop feedback | Competitor research |
| Image gallery | Product imagery | Catalogue enrichment |
Fields listed are those described for a Trendyol product page; availability can vary by page.
| Parameter | Effect | Use it when |
|---|---|---|
| render_js | Executes JavaScript in a headless browser and returns post-render HTML | Prices or stock only appear after scripts run |
| stealth_proxy | Routes through a stealth proxy for stronger bot handling | A target responds aggressively or shows CAPTCHAs |
| country_code | Routes via a residential IP in the chosen country | Content, price, or availability varies by location |
| extract_rules | Pulls structured data with CSS selectors | You need precise, repeatable fields |
| ai_extract_rules | Pulls structured data from a natural-language specification | Selectors are brittle or fields are hard to target |
Parameter names are reproduced exactly as supplied contract literals.
Frequently asked questions
What data can I extract from Trendyol?
Anything visible on the public page can be targeted. Use selector-based rules for precise fields or natural-language rules for AI-driven extraction, and receive structured JSON in return.
How do I get started scraping Trendyol?
Create an account, copy your API key, and send a GET request containing the target URL. The service renders the page, rotates proxies, and returns the result. A trial credit allowance is described in the owner inputs below.
Will I get blocked when scraping Trendyol?
Requests are routed through rotating residential proxies and a real headless browser so they resemble ordinary traffic. If a target responds aggressively, enable the stealth proxy option on that request.
Can I scrape Trendyol without writing code?
Yes. A dashboard request builder accepts a URL and parameters, then produces a ready snippet in Python, Node, Go, PHP, Ruby, or cURL for you to copy.
How do I handle JavaScript when scraping Trendyol?
Set the JavaScript rendering option on the request. The page runs in a headless browser on the server, and the HTML returned reflects the page after scripts have executed.
Can I scrape Trendyol from a specific country?
Yes. Supply a country code so the request is routed through a residential IP in that country, which helps when page content differs by location.