Uzum APIuzum.uz ↗
Access Uzum Market product listings, category trees, seller profiles, and customer reviews via 7 structured endpoints. Real-time data from uzum.uz.
What is the Uzum API?
The Uzum Market API exposes 7 endpoints covering product search, category navigation, seller profiles, and customer reviews from uzum.uz, Central Asia's major e-commerce marketplace. The get_product_details endpoint alone returns over a dozen fields including skuList, rating, description, seller, and photos. Paired with get_seller_info and get_product_reviews, you can build complete product and merchant intelligence pipelines without manually browsing the platform.
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'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace uzum-uz-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.uzum_market_api import UzumMarket, ProductCard, Product, Review
uzum = UzumMarket()
# Browse top-level categories
for category in uzum.categories.list():
print(category.id, category.title, category.icon_link)
# Search for products by keyword
for card in uzum.productcards.search(query="laptop"):
print(card.product_id, card.title, card.min_sell_price, card.rating)
# Get full product details from a search result
first_card = uzum.productcard(product_id=2675043)
product = first_card.details()
print(product.title, product.rating, product.orders_quantity, product.min_sell_price)
print(product.shop.title, product.shop.rating)
for sku in product.sku_list:
print(sku.id, sku.sell_price, sku.available_amount)
# Browse reviews for a product
for review in first_card.reviews.list():
print(review.customer_name, review.rating, review.content)
# Explore a seller's catalog
seller = uzum.seller(id=223)
for card in seller.products(offset=0):
print(card.product_id, card.title, card.min_sell_price)
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 Uzum catalog tree as nested objects, each carrying id, title, iconLink, iconSvg, and children arrays with product counts. Pass any id from that tree directly to get_category_products using the category_id parameter to get paginated product cards with pricing and ratings. Both limit and offset are supported across all listing endpoints for consistent pagination.
Product and Review Data
get_product_details returns a payload.data object with the full product record: title, category, description, rating, photos, skuList (variants), and embedded seller info. For deeper feedback analysis, get_product_reviews fetches the sortedFeedbacks.feedbacks array for a given product_id, where each entry carries a rating, pros, cons, and review content. Pagination is controlled via limit and offset.
Seller Intelligence
get_seller_info accepts a seller URL slug (e.g. uzum-market or world) and returns a profile object with rating, reviews, orders, registrationDate, description, avatar, and banner. If the slug does not match a live seller, the endpoint returns input_not_found. Once you have the numeric seller id from that response, pass it to get_seller_products to page through their full catalog. search_products rounds out discovery — it accepts a free-text query and returns matching product cards from across the entire marketplace, with a total count for result-set sizing.
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 for specific product categories by polling
get_category_productswith a fixedcategory_id. - Build a seller comparison tool using
rating,orders, andregistrationDatefromget_seller_info. - Aggregate customer sentiment by collecting
pros,cons, and ratings fromget_product_reviewsacross competing SKUs. - Map the full Uzum catalog taxonomy by traversing the nested
childrenarrays fromget_categories. - Monitor a seller's active inventory size and pricing using
get_seller_productswith their numericid. - Power a product search feature with
search_productsreturning catalog cards filtered by keyword and paginated viaoffset. - Enrich product records with variant-level data from the
skuListfield returned byget_product_details.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Uzum Market have an official public developer API?+
What does `get_seller_info` return, and what happens if a seller slug is wrong?+
get_seller_info returns a profile object containing id, title, link, banner, avatar, description, rating, reviews, orders, and registrationDate. If the slug you supply does not match any active seller, the endpoint returns input_not_found rather than throwing an error, so your code should check for that value explicitly.Can I retrieve seller-level analytics like monthly sales volume or revenue?+
rating, orders count, registrationDate) and their product listings, but does not expose revenue figures, monthly sales volume, or historical order trends. You can fork this API on Parse and revise it to add an endpoint targeting that data if it becomes available in the source.Is there a way to filter products by price range or specific attributes within a category?+
get_category_products and search_products accept query, limit, and offset but do not support price-range filters or attribute-based faceting as parameters. You can fork this API on Parse and revise it to add filter parameters if the underlying catalog supports them.How does pagination work across listing endpoints?+
search_products, get_category_products, and get_seller_products — use limit and offset integer parameters. The response includes a total integer inside the makeSearch object, which tells you the full result count so you can calculate how many pages remain.