Brand portfolio analysis
Search by brand name and collect every listing returned, with price and stock status. Count products per brand, compare average prices and see which brands 6thStreet pushes hardest in a category.
6thStreet carries a wide mix of sportswear, fashion and lifestyle brands for Gulf shoppers. Query it by brand or keyword and get JSON back: price, discount, brand name and stock status for every result. Use it to see how brands are priced, where competitors undercut you and when popular lines sell out.
# Search by keyword or brand (replace the key)
POST https://api.webfusiondata.com/v1/search
Authorization: Bearer $WFD_API_KEY
{ "site": "6thstreet",
"query": "running shoes",
"country": "AE" }
# Response (sample data, not a live listing)
{
"query": "running shoes",
"result_count": 64,
"results": [
{ "title": "Example Running Shoes",
"brand": "Example Brand",
"price": 249.00, "in_stock": true }
]
}
Sample values for illustration only. Exact field names and nesting for your 6thStreet scope are confirmed in the API reference issued with your key.
A 6thStreet Product Data API turns 6thstreet.com listings into records your systems can use. Send a product link or a keyword and get JSON with brand, title, price, discount and stock status. One schema covers every storefront you are cleared for, so brands and competitors can be compared on equal terms.
We run the collection layer: managed proxies, page rendering, 6thStreet-specific parsing and field validation happen before a response is returned. Large jobs run in the background and arrive by webhook or cloud export, so your integration stays a few HTTPS calls.
Sportswear and fashion brands, distributors and competing retailers use 6thStreet data to check how each brand is priced and discounted, see which brands get shelf space, compare prices against other Gulf stores and catch stock-outs early. Our price monitoring and price intelligence services build on the same data.
From choosing what to collect to loading it into your own systems, in six steps.
Choose product pages, a batch of product URLs, or keyword and brand searches on 6thstreet.com.
List the competitors or brands you want to track and the fields to capture, such as price, discount or stock status.
Build a JSON body with url (or site and query) and a country value for the storefront.
Pick /v1/product for one item, /v1/search for result lists, /v1/monitor for scheduled tracking or /v1/bulk for batches.
Send your API key as a bearer token in the Authorization header.
Use the sandbox first; it returns sample responses and uses no live request credits.
We open the 6thStreet page, render it, extract the fields and validate them. Single lookups answer in the same request.
Bulk jobs give you a job ID to check at /v1/status/:job_id or to receive by webhook.
JSON is the default, and bulk exports can be delivered as CSV or XLSX.
Each record carries its brand, currency and crawled_at timestamp, ready to group and trend.
Write results to a database, update a BI dashboard, raise alerts from webhooks or run recurring checks with monitors.
The Integration and Data Delivery section includes a worked example.
What the 6thStreet Product Data API does for brand, pricing and competitor-intelligence teams, and which parts are documented today versus settled per project.
Search by brand name and collect every listing returned, with price and stock status. Count products per brand, compare average prices and see which brands 6thStreet pushes hardest in a category.
Run the same keyword on 6thStreet and on other retailers you are cleared for, then compare prices side by side. Product matching across retailers is done on brand and title and is agreed per project.
Register a product page for scheduled checks and receive a webhook when the price changes. Each response carries a capture timestamp, so you can build a price history from the first check.
Where a page shows a reduced price or a promotion label, the previous price and discount are returned. Use it to measure discount depth by brand during sale periods and shopping festivals.
Returns the stock status on each page and, where shown, which sizes are available. Monitors can alert you when a line goes out of stock or returns.
Each product is reached by its page URL, so a list of product pages becomes a list of requests to /v1/product. The code shown on the page is returned for matching.
The country parameter selects the storefront for each request, so the same brand can be checked in the UAE, Saudi Arabia or Kuwait. Currencies and the country list are confirmed at onboarding.
Returns the category path and images for each listing, so you can track how a category is merchandised and how the range changes over time.
Use recurring monitors, webhook callbacks or bulk exports to cloud storage, with type-checked JSON, so fresh data arrives without manual pulls.
The fields our 6thStreet product data extraction can return, what each one means and how brand and pricing teams use it. Availability follows what each page displays.
| Data Field | Description | Business Application | Availability |
|---|---|---|---|
product_code | Product code from the page or URL | Product identification, de-duplication | Core |
title | Product name as listed | Catalogue and range checks | Core |
brand | Brand name shown on the listing | Brand share and price-position analysis | Core |
category | Category path shown on the page | Assortment and category benchmarking | Core |
price.amount / price.currency | Current price and its currency code | Competitor price comparison | Core |
discount | Previous price and discount when shown | Promotion depth by brand | Where displayed |
promotion | Promotion label shown on the page | Campaign and sale-event tracking | Confirm at onboarding |
sizes / sizes_in_stock | Sizes listed and which are in stock | Stock-out alerts, size sell-through | Confirm at onboarding |
availability | Displayed stock status | Availability monitoring | Core |
marketplace | Storefront country the record came from | Country-by-country comparison | Core |
images | Product image URLs shown on the page | Visual merchandising checks | Core |
product_url / crawled_at | Page URL and capture timestamp | Reference, freshness checks, time series | Core |
Core = part of the standard field set on our ecommerce API. Where displayed / available / exposed = returned when the listing on that marketplace shows it, so it can be empty for some products. Confirm at onboarding = settled per project. Images and product detail text are also returned. Field names are illustrative; your API reference is the source of truth.
The 6thStreet Product Data API uses the same versioned endpoints as the Ecommerce Scraping API. 6thStreet-specific parameter names that are not yet published are marked as illustrative.
| Endpoint | Purpose | Parameters | Expected response |
|---|---|---|---|
POST /v1/productDocumented |
One 6thStreet product returned as structured data: price, discount, brand, sizes and availability. | Required: urlOptional: country; a dedicated product_code field is a confirm |
One JSON product record, returned synchronously. |
POST /v1/searchDocumented |
Keyword or brand search on 6thstreet.com, returned as a structured result list. | Required: site (e.g. "6thstreet"), queryOptional: country |
JSON with query, result_count and a results array. |
POST /v1/monitorDocumented |
Registers a listing for scheduled price and stock monitoring with webhook notifications. | Required: urlOptional: webhook URL and check frequency names: confirm |
A monitor ID you use to read tracked data later. |
GET /v1/monitor/:idDocumented |
Latest tracked data and change history for one monitored product. | Required: id (path) |
JSON with the current values and recorded changes. |
POST /v1/bulkDocumented |
Submits a batch of URLs for asynchronous processing; results go to storage or a webhook. | Required: list of URLs Optional: delivery destination and format (JSON, CSV or XLSX) names: confirm |
A job ID, then results via webhook or storage export. |
GET /v1/status/:job_idDocumented |
Status and progress of an asynchronous crawl or bulk export. | Required: job_id (path) |
JSON with job state and progress. |
| Situation | Typical HTTP status | How to fix it |
|---|---|---|
Missing or malformed url | 400 | Send the full 6thStreet product URL, including https://. |
| Unsupported site or country value | 400 / 422 | Check site and country against the marketplaces confirmed for your account. |
| Missing or invalid API key | 401 | Send Authorization: Bearer <key> and check the key belongs to the right environment (sandbox or live). |
| Listing not found or no longer available | 404 or an empty record | Check the URL; listings can be removed when a brand line is withdrawn. |
| Request limit exceeded | 429 | Wait, then retry with backoff. Response headers show your remaining quota for the window. |
| Temporary processing failure | 5xx | Retry with exponential backoff; for large volumes use /v1/bulk instead of many synchronous calls. |
Status codes follow common REST conventions (429 is the one shown in our published dashboard example). The exact codes and error bodies are listed in the API reference supplied with your key.
Two common calls and what comes back. Illustrative sample data — not live product information.
curl -X POST https://api.webfusiondata.com/v1/product \
-H "Authorization: Bearer $WFD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://en-ae.6thstreet.com/example-running-shoes.html",
"country": "AE"
}'
curl -X POST https://api.webfusiondata.com/v1/search \
-H "Authorization: Bearer $WFD_API_KEY" \
-d '{"site": "6thstreet", "query": "running shoes", "country": "AE"}'
url or site + query select what to fetch; country selects the marketplace. The key stays in an environment variable — never hard-code it or ship it in client-side code.{
"product_code": "EXAMPLE123",
"marketplace": "AE",
"title": "Example Running Shoes",
"brand": "Example Brand",
"price": { "amount": 249.00, "currency": "AED" },
"discount": { "percent": 24, "list_price": 329.00 },
"availability": "Available",
"rating": 4.5,
"review_count": 215,
"seller": "Example Seller",
"product_url": "https://en-ae.6thstreet.com/example-running-shoes.html",
"crawled_at": "2026-01-15T09:30:00Z"
}
{
"query": "running shoes",
"result_count": 48,
"results": [
{ "title": "Example Running Shoes", "price": 249.00,
"rating": 4.6, "in_stock": true }
]
}
The generic search sample on our Ecommerce Scraping API page uses a flat price number and an in_stock flag, while the product example above nests price under an object. The final 6thStreet schema is confirmed in your API reference.
Choose the marketplace with the country parameter. We do not claim global coverage: the marketplaces available to you are confirmed during onboarding, and requests outside that list are rejected rather than guessed.
| Marketplace | 6thStreet domain | Local currency | Status for the API |
|---|---|---|---|
| United Arab Emirates | 6thstreet.com | AED | Confirm at onboarding |
| Saudi Arabia | 6thstreet.com | SAR | Confirm at onboarding |
| Kuwait | 6thstreet.com | KWD | Confirm at onboarding |
These are the storefronts we plan around, not a coverage guarantee. 6thStreet also serves other Gulf countries; tell us which you need and we will confirm feasibility.
Why it matters: each storefront fixes the currency, the brand range and which optional fields (discount, promotion, sizes) appear. Brand assortment and prices can differ between countries, so tell us which ones matter for your comparison.
What is published today, and what we give you in writing before you go live. We do not publish numeric limits, latency or uptime figures on this page.
| Topic | How it works | Status |
|---|---|---|
| Authentication | Your API key is sent as a bearer token in the Authorization header. Use the sandbox key while testing. | Documented |
| Limits and concurrency | Per-minute limits and concurrent-request allowances scale with your plan; response headers show your remaining quota. Use /v1/bulk for very large volumes. | DocumentedNumbers: your plan |
| Validation and errors | Malformed or missing parameters are rejected with a standard HTTP error (see Endpoints), and responses are schema-checked before delivery. | Exact codes: API reference |
| Timeouts and retries | Set a client timeout and retry reads on 429 and 5xx with exponential backoff. Move long work to /v1/bulk and /v1/status/:job_id, and avoid blind retries of POST /v1/monitor or /v1/bulk. | Recommended practice |
| Pagination | Search returns a result_count and result list. Pagination for deeper results is scoped per project. | Confirm at onboarding |
| Usage monitoring | An account dashboard shows request volume, latency, success rate and job status. | Documented |
A 6thStreet API integration needs a request layer, somewhere to store results and a schedule. The data can then feed pricing tools, databases, BI dashboards, reports and analytics pipelines.
Agree marketplaces, fields and refresh frequency, then call the sandbox with a few sample products.
Put authentication, timeouts and retry backoff in one small client module your whole team reuses.
Upsert records by product code and marketplace, and keep every crawled_at timestamp to build a time series.
Use monitors and bulk jobs, act on webhooks, and connect the table to your dashboards and reports.
import os, sqlite3, requests
API = "https://api.webfusiondata.com/v1/product"
HEADERS = {"Authorization": f"Bearer {os.environ['WFD_API_KEY']}"}
def fetch(path):
body = {
"url": f"https://en-ae.6thstreet.com/{path}",
"country": "AE",
}
r = requests.post(API, json=body, headers=HEADERS, timeout=60)
r.raise_for_status()
return r.json()
db = sqlite3.connect("6thstreet_prices.db")
db.execute("CREATE TABLE IF NOT EXISTS prices "
"(product_code TEXT, amount REAL, currency TEXT, at TEXT)")
for path in ["example-running-shoes.html"]:
item = fetch(path)
db.execute("INSERT INTO prices VALUES (?, ?, ?, ?)", (
item["product_code"],
item["price"]["amount"],
item["price"]["currency"],
item.get("crawled_at"),
))
db.commit()
Default response format for every endpoint.
Bulk export jobs delivered as CSV or XLSX to S3, GCS or your own bucket.
Callbacks when a job completes or a tracked value changes, plus recurring checks through /v1/monitor.
Managed warehouse connectors, client libraries and no-code paths.
Listed on the Ecommerce Scraping API page; availability for your 6thStreet scope is confirmed during onboarding. See also the AI Parser and ecommerce datasets. Related: product availability and MAP monitoring.
A REST API from WebFusion Data that returns 6thstreet.com listings as structured JSON. Send a product URL, or a keyword or brand name and a country, and receive brand, title, price with its currency, discount and availability. It shares endpoints with our Ecommerce Scraping API, so you never run proxies, browsers or parsers.
Core fields are product code, title, brand, category, price and currency, availability, images, product URL, storefront country and a capture timestamp. Discount and sizes come back where the page shows them. Promotion labels, per-size stock and seller details are confirmed per project. See the data fields table.
Yes. Run a brand or category search with /v1/search, collect the results and group them by the returned brand field to count listings and compare average prices. Run it per storefront to see how the brand mix changes between countries. Result depth per query is confirmed at onboarding.
Yes. POST /v1/monitor tracks a product page on a schedule and sends a webhook when the price changes. Run the same for matching products on other retailers you are cleared for and compare the histories. History starts at registration, so store each response with its crawled_at timestamp.
Yes. The stock status on the page is returned with every record, and monitors can alert you when it changes. Sizes are returned where the page lists them, and whether you also get per-size stock levels is confirmed with you before you build on it.
We do not claim wide coverage. The country parameter selects the storefront, and the UAE, Saudi Arabia and Kuwait are where we expect to start. Tell us what you need and we will confirm it at onboarding. See the supported storefronts.
Each request carries your API key as a bearer token in the Authorization header. Every account includes a sandbox for testing with sample responses. Keep the key on your server, in an environment variable or secrets manager, and never in client-side code.
JSON is the default for all endpoints. Bulk export jobs can also be delivered as CSV or XLSX, to S3, GCS or your own bucket. Webhooks, SDKs and database push options are described in Integration and Data Delivery.
Use the Request API Demo button or the form below and tell us the marketplaces, product volume, fields, refresh frequency and delivery format you need. We confirm the scope and set up access, including the sandbox. You can also email sales@webfusiondata.com or book a consultation.

At WebFusionData, we specialize in cutting-edge web scraping solutions to help you unlock valuable insights and drive business growth. Whether you need custom data extraction, real-time monitoring, or large-scale web scraping, our team is here to assist you.
Ready to get started? Contact us for a personalized quote.