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

Uzum Nasiya Partner API

REST API for partner integration with the Uzum Nasiya installment (BNPL) service. Buyer registration through an Uzum Nasiya WebView, buyer status and credit limit checks, basket pre-calculation of installment terms, contract creation, SMS-code activation, and contract confirmation or cancellation. Bearer token authentication.

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

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

8 operations 8 paths 35 schemas 8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.2
Base URL
https://merchants-api.uzumnasiya.uz
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Uzum Nasiya Partner 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 35

The contract defines 35 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.

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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uzum-nasiya-openapi.yaml Raw ↑
Where this information came from

This is an independent, third-party profile of Uzum Nasiya Partner 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.