Arzonapteka APIarzonapteka.uz ↗
Access medicine prices, pharmacy offer counts, and regional data from arzonapteka.uz via 3 endpoints covering regions, popular products, and product detail.
What is the Arzonapteka API?
The arzonapteka.uz API provides structured access to Uzbekistan's pharmacy price comparison data across 3 endpoints. Use list_regions to retrieve the full region tree with pharmacy counts per node, list_popular_products to pull the popular medicines rail with minimum UZS prices per region, and get_product to fetch a single medicine's composition, prescription status, minimum price, and pharmacy offer count for any geographic scope.
curl -X GET 'https://api.parse.bot/scraper/3530b4fb-2ff1-4e7b-bc20-f2df7691ec43/list_regions?lang=en' \ -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 arzonapteka-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.
"""Walkthrough: ArzonApteka SDK — browse regions, popular medicines, and product details."""
from parse_apis.arzonapteka_uz_api import ArzonApteka, ProductNotFound
client = ArzonApteka()
# 1. Fetch the region tree and pick the first child region (a city/oblast).
top = client.regions.list(limit=1).first()
if top is None:
raise SystemExit("no regions returned")
city = top.children[0]
print(f"Region: {city.name} (id={city.region_id}, pharmacies={city.pharmacy_count})")
# 2. List popular-product sections for that region.
section = client.sections.list(region_id=city.region_id, limit=1).first()
if section is None:
raise SystemExit("no sections returned")
print(f"Section '{section.key}' has {len(section.products)} products")
# 3. Drill into the first product summary to get full detail.
summary = section.products[0]
print(f" {summary.name} — {summary.min_price} {summary.currency}, "
f"{summary.offers_count} offers, in_stock={summary.in_stock}")
product = summary.details(region_id=city.region_id)
print(f" Full: {product.name}, form={product.form}, "
f"package_quantity={product.package_quantity}")
for ingredient in product.active_ingredients:
print(f" ingredient: {ingredient.name}, dosage={ingredient.dosage_value}")
# 4. Point lookup by slug (using the slug we already discovered).
try:
same = client.products.get(slug=product.slug)
print(f" Looked up: {same.name}, manufacturer={same.manufacturer}, "
f"country={same.country}")
except ProductNotFound:
print(" product not found")
print("exercised: regions.list / sections.list / summary.details / products.get")
Returns the full region tree of Uzbekistan used by the site (country > region/city > district), each node with its numeric region_id, slug, coordinates and the number of pharmacies it covers. One round trip; a few dozen nodes total. region_id values feed the region_id input of the other endpoints.
| Param | Type | Description |
|---|---|---|
| lang | string | Language of region names. |
{
"type": "object",
"fields": {
"regions": "array of top-level region nodes; each node has region_id (integer), slug, name, latitude, longitude, pharmacy_count (integer, pharmacies in this region) and a nested children array of the same shape"
},
"sample": {
"data": {
"regions": [
{
"name": "Uzbekistan",
"slug": "uzbekistan-2",
"children": [
{
"name": "City Of Tashkent",
"slug": "gorod-tashkent-2106",
"children": [
{
"name": "Almazar District",
"slug": "almazarskiy-rayon-2116",
"children": [],
"latitude": 41.32723356243705,
"longitude": 69.18764539440733,
"region_id": 2116,
"pharmacy_count": 95
}
],
"latitude": 41.250487562365635,
"longitude": 69.21758204545955,
"region_id": 2106,
"pharmacy_count": 963
}
],
"latitude": 41.393544999998866,
"longitude": 63.36148883011097,
"region_id": 2,
"pharmacy_count": 1977
}
]
},
"status": "success"
}
}About the Arzonapteka API
Region and Geography Coverage
The list_regions endpoint returns the complete Uzbekistan region hierarchy — country, region/city, and district — as a tree of nodes. Each node carries a numeric region_id, a slug, latitude and longitude coordinates, and a pharmacy_count indicating how many pharmacies operate in that area. The region_id values from this endpoint are the filter input for both other endpoints. Passing region_id: 2 scopes prices to all of Uzbekistan; omitting it has the same effect.
Popular Products by Region
list_popular_products returns the site's curated popular medicines rail for a given region. Each entry in the products array includes product_id, slug, name, manufacturer, min_price in UZS, an in_stock boolean, and a count of pharmacy offers. Prices and offer counts shift with region_id, so the same medicine may show a different minimum price in Tashkent versus a district-level scope. The response also echoes back the region_id used for the price calculation.
Product Detail
get_product takes a product slug (sourced from list_popular_products) and an optional region_id. It returns identity fields (product_id, name, slug, commercial name), composition data (active ingredients with dosage), form (dosage form), package quantity, manufacturer, country, prescription status, in_stock, min_price in UZS, currency (always UZS), and an array of images. The region_id field in the response is null when no region was supplied, confirming that pricing reflects nationwide coverage.
The Arzonapteka API is a managed, monitored endpoint for arzonapteka.uz — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when arzonapteka.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 arzonapteka.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 minimum medicine prices across Uzbekistan regions using min_price and region_id filtering
- Build a pharmacy offer density map using pharmacy_count and coordinates from list_regions
- Monitor popular medicine availability and stock status via the in_stock flag in list_popular_products
- Compare prescription vs. non-prescription medicine pricing using the prescription field from get_product
- Aggregate manufacturer presence across popular products using the manufacturer field
- Identify which districts have the most pharmacy coverage using pharmacy_count at the district node level
- Build a medicine lookup tool keyed on active ingredient composition returned by get_product
| 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.