Authorized protocol analysis for Uzbekistan’s unified electronic trading stack: catalog ingestion, lot detail normalization, and bid-state monitoring aligned with transparency rules.
The mobile client exposes category trees, enriched lot cards, and participation flows that sit on top of regulated trading procedures. When you need repeatable exports—rather than manual screenshots—we map those screens to stable request/response contracts, pagination, and change detection suitable for reconciliation dashboards.
Each module below names a concrete dataset, names the originating surface in the refreshed e-auksion client, and states a downstream job it unlocks. We avoid hand-wavy claims: if a field is not exposed to authenticated users, we document the gap instead of fabricating an endpoint.
Ingests hierarchical browse paths (parent/child nodes) from the expanded search experience described in the Uzbek release notes. Finance controllers reuse the same tree in internal SKU mapping so capital projects line up with published government asset classes.
Pulls the redesigned lot detail layout—headline attributes, imagery, and narrative blocks—and normalizes them into JSON segments for CRM systems that must brief investment committees before bid deadlines.
Models phases such as announcement, active bidding, and settlement checkpoints implied by Cabinet Resolution 18 workflows. Risk teams attach policy rules (minimum participants, payment windows) to each transition.
Persists each authenticated price offer with user references for dispute resolution. Legal teams export CSV timelines that mirror the transparency goals highlighted in Uzbekistan’s public-sector modernization articles.
Where payment instructions surface in-app, we capture masked account metadata and due-date fields so treasury can orchestrate bank transfers without scraping unstructured PDFs—useful when comparing OpenFinance-style settlement rails across ministries.
Replays anonymized crowd metrics (participant counts, leading price bands) for investor relations microsites, echoing the public monitoring mechanisms referenced in independent coverage of the national trading stack.
Automated pulls every few minutes replace manual checks of the convenient bidding interface, shrinking the window between a rival bid and your counter-offer.
Each synchronization stores HTTP fingerprints, token scopes, and payload hashes so auditors can prove which dataset version backed a regulatory filing.
Because e-auksion ships on Android (uz.auction.v2) and iOS, we document divergent TLS pinning or attestation behaviors instead of assuming identical stacks.
The 2025 UI overhaul changed typography and card layouts; our harness runs visual diff snapshots so breakage alerts arrive before your nightly ETL job silently ingests garbage.
Thumbnails below reflect the refreshed visual system referenced in the official changelog: brighter lot storytelling, denser filters, and faster navigation between asset classes. Click any tile to inspect the full-resolution capture without leaving the page.
The inventory synthesizes the Uzbek-language feature bulletin (new home layout, expanded search, performance tuning) with public reporting on nationwide electronic auctions. Rows cite the user-visible origin so compliance officers understand provenance.
| Data type | Source (screen / feature) | Granularity | Typical use |
|---|---|---|---|
| Category facets & keyword filters | Expanded search & browse rails called out in the 2025 changelog | Per category node + filter tuple | Master data governance teams align internal taxonomies with published government asset classes before bidding. |
| Lot static attributes | Redesigned lot detail cards (headline specs, imagery) | Per lot revision | Investment committees build valuation memos with authoritative descriptions instead of copy-paste from chat threads. |
| Live offer stream | Participation interface highlighted as more convenient in the release notes | Per bid event (timestamp, amount, anonymized handle) | Market surveillance squads correlate spikes with macro news for OpenData dashboards shared with regulators. |
| Auction calendar metadata | Home dashboard tiles after the UI refresh | Per session window (open/close UTC offsets) | ERP schedulers reserve treasury staff and notaries when multiple high-value lots overlap. |
| Payment & escrow cues | Post-bid instructions referencing Cabinet timelines (10–15 business days in public summaries) | Per awarded contract milestone | Treasury matches outbound wires with documented schedules, mirroring OpenFinance reconciliation practices. |
| Digital outcome artifacts | Cross-links to my.gov.uz services that issue winning protocols for E-AUKSION trades | Per successful auction | Legal archives automatically fetch confirmation IDs once the mobile client surfaces deep links. |
Context: An agency project office must monitor dozens of simultaneous asset disposals. Data/API focus: Category feeds plus lot JSON bundles pulled hourly. OpenData mapping: Published objects become machine-readable records that feed a national transparency portal alongside CSV dumps from legacy registers.
Context: A corporate bank pre-approves customers who bid on high-ticket infrastructure. Data/API focus: Authenticated session tokens scoped to the user’s active bids, combined with masked settlement instructions. OpenFinance angle: Mirrors PSD2-style consent: the customer authorizes read-only exposure of bid exposure to credit analysts for 72 hours.
Context: Cross-border participants highlighted in English-language investment outreach need evidence packs. Data/API focus: Multilingual lot descriptions where available, attachment hashes, and UTC-normalized timelines. OpenData angle: Packages land in an S3 bucket tagged with PDPL retention policies for Uzbek citizen PII.
Context: Conglomerates buy both specialty plates and general state assets. Data/API focus: Normalized auction_channel enum distinguishing e-auksion from Avtoraqam feeds. Landscape mapping: Supports the 2025 expectation that procurement teams will juggle the new Xarid mobile stack while legacy e-auksion lots remain live.
Context: Insurers track disposed assets that previously secured policies. Data/API focus: Lot IDs tied to cadastral references when displayed. OpenData tie-in: Change-detection webhooks push notifications to underwriting systems the moment a lot flips to “sold,” triggering policy updates without manual broker calls.
Snippets illustrate contract shapes we deliver after protocol analysis. Paths are illustrative; final routes follow whatever gateway you deploy in front of the analyzed client traffic.
POST /integrations/e-auksion/v1/session
Content-Type: application/json
{
"grant_type": "authorization_code",
"code": "<ONE_TIME_MOBILE_CODE>",
"device_profile": {
"platform": "android",
"package": "uz.auction.v2",
"attestation": "<PLAY_INTEGRITY_TOKEN>"
}
}
201 Created
{
"access_token": "eyJ...",
"expires_in": 3600,
"scopes": ["catalog:read", "bids:read"],
"subject_type": "legal_entity"
}
GET /integrations/e-auksion/v1/lots?category=real_estate&updated_since=2026-04-10T00:00:00Z
Authorization: Bearer eyJ...
200 OK
{
"next_cursor": "opaque",
"items": [
{
"lot_id": "UZ-EA-88421",
"title": "Regional logistics hub",
"reserve_visible": true,
"currency": "UZS",
"attrs": {"area_sqm": 12400}
}
]
}
POST https://customer.example/hooks/e-auksion
EA-Signature: t=1713345123,v1=d14a0280...
{
"event": "bid.superseded",
"lot_id": "UZ-EA-88421",
"previous_amount": "18500000000",
"new_amount": "19250000000",
"occurred_at": "2026-04-17T04:59:11Z"
}
// Error handling when upstream throttles
429 Too Many Requests
{
"error": "rate_limited",
"retry_after": 30,
"trace_id": "7f1c-b12a"
}
Electronic auctions in Uzbekistan operate under Cabinet of Ministers Resolution No. 18 (January 12, 2022) and subsequent amendments tracked through late 2025, which codify notice periods, minimum participants, and settlement discipline. Those statutory obligations shape what data may be shown publicly versus behind authenticated accounts.
Personal data handling must align with the Law of the Republic of Uzbekistan “On Personal Data” (ZRU-547, effective October 1, 2019) and its 2021 localization amendments requiring citizen data to remain on territory-approved infrastructure. Our integration blueprints include data-flow diagrams for operators, owners, and subjects under that law’s vocabulary.
Where financial institutions participate, we recommend layering card/account data minimization practices comparable to open-banking consent receipts—even when the underlying transport is not literal PSD2—so downstream processors log purpose limitation and retention windows.
A pragmatic pipeline starts with the official mobile client as the controlled user interface, passes traffic through a hardened ingestion tier that performs token refresh and backoff, lands normalized events in a regional object store, and finally fans out to analytics warehouses or customer-facing REST/GraphQL facades. Each hop emits structured audit logs so personalization agencies can trace lawful bases.
Primary users include Uzbek legal entities bidding on privatized assets, individual entrepreneurs chasing specialized inventory, and increasingly foreign investors enabled by streamlined digital signature onboarding described in English-language investment briefings. The Android distribution exceeds half a million installs with strong review velocity, while the iOS listing underscores the Business category placement—signals that decision makers expect phone-first workflows. Because the April 2025 Play Store update explicitly calls out faster performance, latency-sensitive traders now assume sub-second refreshes, which our monitoring agents respect via adaptive polling instead of aggressive hammering.
Keyword bridges below help procurement engineers discover our studio when they research adjacent mobility products. Each paragraph stays descriptive—no rankings or negative comparisons.
UzEx’s plate-focused auction app exposes high-frequency bidding and payment history patterns comparable to e-auksion’s asset lots. Teams integrating both often want unified webhook schemas so treasury sees a single ledger of specialty government sales.
Launched in 2025 for electronic state procurement and e-shop trading, Xarid carries contract award metadata that complements e-auksion’s broader asset mix. Joint dashboards blend supplier qualification data with auction outcomes.
This marketplace for premium mobile numbers generates SKU-like listings with tariff nuances. Catalog normalization routines written for MobilRaqam frequently port to e-auksion’s telecommunications-related lots.
Operated alongside Republic Property Center workflows, the portal surfaces aggregate statistics on live and completed auctions. Data teams mirror its headline counters against mobile-derived totals to catch drift.
Agricultural commodity boards publish seasonal supply data. Risk models that ingest Agro UzEx pricing benefit when e-auksion land auctions include farming parcels tied to the same indices.
The broader Uzbek commodity exchange stack handles futures-style instruments. Institutions already streaming UzEx ticks extend their bus architecture to e-auksion for illiquid asset diversification metrics.
Web-first property workflows sometimes publish PDF protocols while the mobile app emphasizes interactive cards. Integrations stitch both channels so document management systems retain immutable files plus structured JSON.
Citizens obtain winning protocols through public service APIs tied to E-AUKSION. Linking mobile session context with my.gov.uz reference numbers closes the loop for compliance archives without duplicate data entry.
Long-tail planners often search for phrases like e-auksion catalog export API or Uzbekistan electronic auction webhook integration; the steps below translate those intents into an engagement-ready checklist. We begin every mandate by confirming whether your use case requires read-only market intelligence or authenticated trader actions, because the authorization stack differs materially.
Optional hosted endpoints follow a pay-per-call model: you receive HTTPS routes that wrap our maintained workers, while metered billing tracks only successful 200-level payloads.
Source code delivery from $300 covers a focused slice—typically read-only catalog sync plus documentation. Broader mandates that include authenticated bid placement, redundant data centers, or 24/7 paging inherit additional sprint fees quoted after discovery.
Deliverables explicitly mention e-auksion bid history export, OpenData auction catalog integration, and Uzbekistan escrow timeline monitoring so procurement stakeholders recognize the mapping between marketing language and engineering artifacts.
We are a technical services studio specializing in authorized app interface integration, reverse-engineering-resistant protocol analysis, and OpenData delivery. Our engineers previously built ingestion stacks for banks, exchanges, and mobility marketplaces across several continents.
Share your target app (e-auksion) plus concrete requirements—catalog depth, bid latency, or cross-ministry reporting—and we respond with a scoped proposal.
Do you need official APIs?
Can you guarantee bid placement?
How do you avoid duplicate content with other landing pages?
Official Uzbek release notes for the renewed e-auksion mobile application list these changes: a redesigned main screen, broader search and sorting with category navigation for quickly discovering property and objects, a brighter layout for studying lot information, faster overall performance, and a more convenient interface for participating in auction trades. The description positions the client as the refreshed front-end to the national electronic commerce platform that digitizes competitive bidding for state and municipal assets.
Because the text is distributed in Uzbek (Cyrillic script), international delivery teams rely on our bilingual annotations to ensure field labels in exported JSON preserve original semantics—critical when auditors compare mobile screenshots with notarized translations.
uz.auction.v2