Uzum APIuzum.uz ↗
Access Uzum.uz product listings, category trees, pricing in UZS, seller profiles, and customer reviews via 8 structured REST endpoints.
What is the Uzum API?
The Uzum Market API exposes 8 endpoints covering the full catalog of Uzbekistan's largest online marketplace. You can retrieve the complete category tree, search products by keyword, pull SKU-level pricing in UZS tiyin, and fetch paginated customer reviews — all in structured JSON. The get_product_details endpoint alone returns over 10 fields including seller info, SKU availability, HTML description, and photo URLs.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/854c74bc-8ffb-43f1-9412-d5c355c8c866/get_categories' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve the full category tree from the Uzum catalog. Returns all top-level categories with nested children arrays containing subcategories and product counts. Categories are hierarchical - each top-level category has children which may have their own children.
No input parameters required.
{
"type": "object",
"fields": {
"payload": "array of top-level category objects each containing id, title, iconLink, iconSvg, and nested children arrays with subcategories"
},
"sample": {
"data": {
"payload": [
{
"id": 2894,
"title": "Mebel",
"iconSvg": "<svg.../>",
"children": [
{
"id": 17616,
"eco": false,
"adult": false,
"title": "Karavot va matraslar",
"children": [
{
"id": 14557,
"title": "Matraslar",
"children": [],
"productAmount": 74
}
],
"productAmount": 1
}
],
"iconLink": "https://static.uzum.uz/banners/mebel902.png"
}
],
"timestamp": "2026-06-10T09:43:30.497593188"
},
"status": "success"
}
}About the Uzum API
Category and Product Discovery
get_categories returns the full hierarchical category tree with each node carrying an id, title, iconLink, iconSvg, and nested children arrays. Those category IDs feed directly into get_category_products, which accepts category_id, limit, and offset to paginate through product cards. Each card includes productId, title, minSellPrice, minFullPrice, rating, and feedbackQuantity. search_products works similarly but takes a query string instead of a category ID, returning a total count alongside the items array.
Product Detail and Reviews
get_product_details accepts a product_id and returns the richest response in the API: a shop object with seller id, title, and rating; a skuList array where each SKU carries availableAmount, fullPrice, and sellPrice; photos with high- and low-resolution links; a description field in HTML; and both minFullPrice and minSellPrice in UZS tiyin (divide by 100 to get som). get_product_reviews returns an array of feedbacks for a given product — each entry includes customerName, rating, content, pros, cons, dateCreated, and datePublished as Unix timestamps in milliseconds. Pagination uses offset divided by limit to derive the page number internally.
Seller Data
The seller workflow is two-step. get_sellers takes a query string and returns up to 20 matching shops with id, title, link (slug), avatar URLs, rating, reviewCount, orderCount, and an official boolean flag. Pass the returned slug to get_seller_info for the full profile: banner, avatar, description, registrationDate (Unix ms), and sellerAccountId. The numeric id from that response is what get_seller_products requires to paginate through a seller's listings.
Pricing and Currency Notes
All price fields (minSellPrice, minFullPrice, sellPrice, fullPrice) are expressed in UZS tiyin, the sub-unit of the Uzbek som where 1 som = 100 tiyin. Convert before display. There is no currency parameter — prices are always in UZS.
The Uzum API is a managed, monitored endpoint for uzum.uz — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when uzum.uz changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official uzum.uz API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track price changes on specific SKUs by polling
get_product_detailsand comparingminSellPriceover time. - Build a category-level price index by combining
get_categoriesIDs with paginatedget_category_productscalls. - Aggregate seller reputation data by pulling
rating,reviewCount, andorderCountfromget_seller_info. - Run sentiment analysis on product reviews using the
pros,cons, andcontentfields fromget_product_reviews. - Map the full Uzum catalog hierarchy for taxonomy research using the nested
childrenarrays inget_categories. - Identify top-rated sellers in a product segment by combining
get_sellerssearch withget_seller_productslisting counts. - Monitor stock availability per variant by inspecting
availableAmountin theskuListarray fromget_product_details.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Uzum Market have an official developer API?+
What does `get_product_details` return that the listing endpoints don't?+
get_product_details returns the full SKU list with per-variant availableAmount, fullPrice, and sellPrice; an HTML description; a shop object with the seller's id, title, and rating; and multiple photos with both high- and low-resolution URLs. Product listing endpoints like search_products and get_category_products return only summary card data: productId, title, aggregate pricing, rating, and feedbackQuantity.How does pagination work across the different endpoints?+
search_products, get_category_products, and get_seller_products all use offset-based pagination via offset and limit parameters, and each returns a total field so you can compute total pages. get_product_reviews also accepts offset and limit, but the offset is divided by limit internally to derive a page number, so setting offset to values that are not multiples of limit may return unexpected page boundaries.Does the API return promotional or campaign data such as flash sales or discount banners?+
minSellPrice vs minFullPrice), category structure, seller profiles, and reviews. Campaign metadata, flash-sale countdowns, or banner content are not included in any current endpoint. You can fork this API on Parse and revise it to add an endpoint targeting promotional data.Can I get order history or buyer transaction data through the API?+
orders in get_seller_info) but does not return individual order records, buyer identities, or transaction details. You can fork this API on Parse and revise it to surface additional seller analytics if the source exposes them publicly.