How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Uzum

Uzum API MFO API

The API MFO API from Uzum — 8 operation(s) for api mfo.

Documentation Provider Profile APIs.io OpenAPI GitHub

Uzum API MFO API is one of 19 APIs that Uzum publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include API MFO. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 8 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.0.2.

Requests are made against a single base URL, https://merchants-api.uzumnasiya.uz.

8 operations 8 paths 26 schemas 8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.2
Base URL
https://crossborder.transfer.uz
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Uzum API MFO API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth).

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 8 POST. Each is listed below with its method, path, parameters, and response codes.

API MFO 8
POST
/api/v1/buyers/check-status
Проверка статуса пользователя
checkBuyerStatus body → 200400401403
POST
/api/v1/orders/calculate
Калькуляция товаров
calculateOrder body → 200400401403
POST
/api/v1/orders
Создание договора
createOrder body → 200400401403
POST
/api/v1/contracts/check-status
Проверка статуса договора
checkContractStatus body → 200400401403
POST
/api/v1/contracts/confirm
Подтверждение договора
confirmContract body → 200400401403
POST
/api/v1/contracts/cancel
Полная отмена договора
cancelContract body → 200400401403
POST
/v3/buyers/send-code-sms
Отправка SMS-кода для активации договора
sendContractSmsCode body → 200400401403
POST
/v3/buyers/check-code-sms
Подтверждение SMS-кода активации договора
verifyContractSmsCode body → 200400401403

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are CalculatedTariff (21 properties), BuyerStatusDataMFO (11 properties), ContractStatusData (10 properties), CreatedContractProduct (9 properties). Each schema is shown below with its type and property counts.

ContractStatusData
object
Детальная информация о договоре.
10 properties 6 required
CancelContractResponse
object
Ответ метода полной отмены договора.
4 properties 4 required
BuyerStatusResponseMFO
object
Ответ метода проверки статуса пользователя.
3 properties 3 required
CreateOrderProduct
object
7 properties 5 required
CheckContractStatusResponse
object
Ответ метода проверки статуса договора.
3 properties 3 required
CreateOrderRequest
object
5 properties 3 required
BuyerStatusRequest
object
1 property 1 required
CancelContractRequest
object
Запрос на полную отмену договора.
1 property 1 required
CreateOrderData
object
4 properties 4 required
CalculateRequest
object
2 properties 2 required
AvailablePeriodMFO
object
Тарифный период, доступный пользователю.
6 properties 6 required
BuyerStatusDataMFO
object
Объект с информацией о пользователе и доступных ему тарифных периодах.
11 properties 7 required
VerifySmsCodeResponse
object
Ответ подтверждения SMS-кода.
3 properties 3 required
SendSmsCodeRequest
object
Запрос на отправку SMS-кода.
2 properties 2 required
CalculateProductRequest
object
3 properties 3 required
VerifySmsCodeRequest
object
Запрос на подтверждение SMS-кода.
3 properties 3 required
CheckContractStatusRequest
object
Запрос на получение информации о договоре.
1 property 1 required
CalculatedProduct
object
6 properties 6 required
SendSmsCodeResponse
object
Ответ метода отправки SMS-кода.
3 properties 3 required
CalculateResponse
object
3 properties 3 required
ConfirmContractErrorResponse
object
Ошибка подтверждения договора.
4 properties 4 required
ConfirmContractResponse
object
Ответ при успешной активации договора.
4 properties 4 required
CalculatedTariff
object
21 properties 13 required
ConfirmContractRequest
object
Запрос на подтверждение (активацию) договора.
1 property 1 required
CreateOrderResponse
object
3 properties 3 required
CreatedContractProduct
object
9 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-api-mfo-api-openapi.yml Raw ↑

Other APIs Uzum publishes across the network.

Uzum BaaS Payment Hub
AE Profile APIs.io
Uzum Market Seller API
AE Profile APIs.io
Uzum Auxiliary Methods API
AE Profile APIs.io
Uzum Back-to-back Payment API
AE Profile APIs.io
Uzum Check Service Status API
AE Profile APIs.io
Uzum Common methods API
AE Profile APIs.io
Uzum Cross-border payments API
AE Profile APIs.io
Uzum Fiscalization API
AE Profile APIs.io
Uzum From Uzbekistan API
AE Profile APIs.io
Uzum Information retrieval API
AE Profile APIs.io
Uzum Managing Credit Cards Bindings API
AE Profile APIs.io
Uzum Methods API
AE Profile APIs.io
#API MFO
← Back to U APIs
API Details
ID
uzum:uzum-api-mfo-api
Base URL
https://crossborder.transfer.uz
Docs
https://developer.uzumbank.uz/en/checkout
Provider
Uzum
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=uzum-api-mfo-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/uzum-api-mfo-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Uzum API MFO API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.