Versions Compared

Old Version 4

changes.mady.by.user Оксана Нечепоренко

Saved on

compared with

New Version Current

changes.mady.by.user Оксана Нечепоренко

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Warning

Will be commissioned in the 3rd quarter of 2024

...

Notifications about changes in the borrower’s credit history criteria, which are of interest to you

...

Http Method

POST

Request URL

https://secure.ubki.ua/b2/monit/api4monit

Request

Code Block
<?xml version='1.0' encoding='windows-1251'?>
<doc>
  <request rtype="">
    <auth login="" pass="" />
    <i dates="" datep="" state="" id="" pullname="" worktime="" workperiod="" seltrigger="" selinns="" />
  </request>
</doc>

Request params

Request type attributes

rtype

Request type (SRCH - Pool search, CRPL - Pool creation, ACPL - Pool activation, LSTS - Trigger list)

Authorization attributes

login

Login

pass

Password

Response params

stateproc

Pool processing status. List of possible values (n - Waiting for processing, s - Processing in progress, r - Processed)

Get a list of pools specifying SRCH filters

Request

Code Block
<?xml version='1.0' encoding='windows-1251'?>
<doc>
  <request rtype="SRCH">
    <auth login="login" pass="pass" />
    <i dates="" datep="" state="" id="">
    </i>
  </request>
</doc>

Request params

rtype

SRCH is a sign of the mode of receiving the list of pools

dates

Filter date from

datep

By date

state

Pool status. List of possible values (n - not active, r - active, e - closed by term, s - forcibly stopped, empty - filter disabled)

id

ID of the pool. When requesting a pool ID, a list of TIN in this pool is also displayed

Response

  1. Unsuccessful search

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>NODATA
</doc>

2. Search with and without filters

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>
  <pull id="1" pullname="" worktime="3" workperiod="dd" state="e" stateproc="r" datetimefinish="12.11.2010 10:47:14" createdate="12.08.2010 10:47:14" editdate="26.08.2010 16:33:53">
    <trigger idtr="1" trname="Trigger: Occurrence of arrears up to 7 days">
    </trigger>
    <trigger idtr="2" trname="Trigger: The occurrence of a delay of 7-30 days">
    </trigger>
    <trigger idtr="3" trname="Trigger: Occurrence of arrears from 30-60 days">
    </trigger>
    <trigger idtr="4" trname="Trigger: Overdue occurrence from 60-90 days">
    </trigger>
    <trigger idtr="5" trname="Trigger: Occurrence of delay over 90 days">
    </trigger>
    <trigger idtr="6" trname="Trigger: New credit">
    </trigger>
    <trigger idtr="7" trname="Trigger: Closing arrears on credit">
    </trigger>
    <trigger idtr="8" trname="Trigger: Credit closing">
    </trigger>
  </pull>
  <pull id="2" pullname="" worktime="3" workperiod="dd" state="e" stateproc="r" datetimefinish="13.11.2010 09:49:36" createdate="13.08.2010 09:49:36" editdate="13.08.2010 09:53:19">
    <trigger idtr="1" trname="Trigger: Occurrence of arrears up to 7 days">
    </trigger>
    <trigger idtr="2" trname="Trigger: The occurrence of a delay of 7-30 days">
    </trigger>
    <trigger idtr="3" trname="Trigger: Occurrence of arrears from 30-60 days">
    </trigger>
    <trigger idtr="4" trname="Trigger: Overdue occurrence from 60-90 days">
    </trigger>
    <trigger idtr="5" trname="Trigger: Occurrence of delay over 90 days">
    </trigger>
    <trigger idtr="6" trname="Trigger: New credit">
    </trigger>
    <trigger idtr="7" trname="Trigger: Closing arrears on credit">
    </trigger>
    <trigger idtr="8" trname="Trigger: Credit closing">
    </trigger>
    <trigger idtr="10" trname="Trigger: Search in court decisions">
    </trigger>
    <trigger idtr="39" trname="Trigger: Credit card credit limit change by 20%">
    </trigger>
  </pull>
</doc>

3. Search by ID

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>
  <pull id="23" pullname="Test" worktime="1" workperiod="dd" state="n" stateproc="r" datetimefinish="30.06.2011 16:23:32" createdate="30.05.2011 16:23:32" editdate=" ">
   <trigger idtr="2" trname="Trigger: The occurrence of a delay of 7-30 days">
    </trigger>
    <trigger idtr="3" trname="Trigger: Occurrence of arrears from 30-60 days">
    </trigger>
    <data inn="3208213498">
    </data>
    <data inn="2131527032">
    </data>
    <data inn="2752222291">
    </data>
    <data inn="1952511230">
    </data>
    <data inn="3165312479">
    </data>
    <data inn="3094609866">
    </data>
    <data inn="3168918767">
    </data>
  </pull>
</doc>

Creating a CRPL pool

Request

Code Block
<?xml version='1.0' encoding='windows-1251'?>
<doc>
  <request rtype="CRPL">
    <auth login="" pass="" />
    <i pullname="" worktime="" workperiod="" seltrigger="" selinns="">
    </i>
  </request>
</doc>

Request params

rtype

CRPL is a feature of the pool list retrieval mode

pullname

The name of the pool

worktime

Pool expiration date. Possible values ​​(-1 - Single check, 1 - 1 month, 3 - 3 months, 6 - 6 months, 9 - 9 months, 12 - 12 months)

workperiod

Periodicity of the bypass. Possible values ​​(dd - daily, mm - once a month, wk - once a week)

seltrigger

List of triggers. The trigger id(s) must be set via the | separator. Possible values ​​are -

1 - Trigger: Occurrence of arrears up to 7 days

2 - Trigger: The occurrence of a delay of 7-30 days

3 - Trigger: The occurrence of a delay of 30-60 days

4 - Trigger: Occurrence of arrears of 60-90 days

5 - Trigger: Occurrence of arrears of more than 90 days

6 - Trigger: New loan

7 - Trigger: Closing the default on the loan

8 - Trigger: Closing the loan

10 - Trigger: Search in court decisions

39 - Trigger: Credit card credit limit change by 20%).

For example: seltrigger = "1 | 3 | 5 | 10 |", you can specify types of constituent triggers.

selinns

List of TIN for monitoring. It is necessary to install TIN through the separator |. For example: selinns = "3052410431 | 3052410432 |. Only unique TIN are added to the pool, duplicates will be ignored when saved

Response

In the event of a creation error, the XML will be of the form:

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>[Error text]
</doc>

Indication of a successful pool creation:

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>
  <pull id="54" pullname="ХХХХХ" worktime="1" workperiod="mm" state="n" stateproc="n" datetimefinish="" createdate="" editdate="">
    <trigger idtr="1" trname="">
    </trigger>
    <trigger idtr="2" trname="">
    </trigger>
    <trigger idtr="3" trname="">
    </trigger>
    <data inn="3052410433">
    </data>
    <data inn="2834523452">
    </data>
    <data inn="2834523453">
    </data>
  </pull>
</doc>

Activation of the ACPL pool

Request

Code Block
<?xml version='1.0' encoding='windows-1251'?>
<doc>
  <request rtype="ACPL">
    <auth login="" pass="" />
    <i id="">
    </i>
  </request>
</doc>

Request params

rtype

ACPL - sign of the mode of removing the list of bullets

id

Pool ID

Response

In the event of a creation error, the XML will be of the form:

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>[Error text]
</doc>

Indication of a successful pool creation:

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>
  <pull id="52" pullname="" worktime="" workperiod="" state="r" stateproc="n" datetimefinish="" createdate="" editdate="" />
</doc>

Retrieve the list of requests to the LSTS pool

Request

Code Block
<?xml version='1.0' encoding='windows-1251'?>
<doc>
  <request rtype="LSTS">
    <auth login="" pass="" />
    <i id="">
    </i>
  </request>
</doc>

Request params

rtype

LSTS is a feature of the pool list retrieval mode

id

Pool ID

Response

If there are no triggers:

Code Block
<dones iddone="" donedate="" idtr="" inn="" dealreference="" fio="" db="" typecredit="" dealamount="" dealcurr="" dealamtcurr="" 
dealamtexp="" dealdaysexp="" remark="" />

List of triggers:

Code Block
<?xml version="1.0" encoding="windows-1251"?>
<doc>
  <dones iddone="469687" donedate="19.10.2017 10:18:14" idtr="2" inn="2598821476" FIOua="КОРДОНЕЦЬ ВАЛЕНТИН ОЛЕКСАНДРОВИЧ" 
  FIOru="КОРДОНЕЦЬ ВАЛЕНТИН ОЛЕКСАНДРОВИЧ" dealreference="236083" fio="(КОРДОНЕЦЬ ВАЛЕНТИН ОЛЕКСАНДРОВИЧ) [КОРДОНЕЦЬ ВАЛЕНТИН ОЛЕКСАНДРОВИЧ]" 
  db="25.02.1971" typecredit="010" dealamount="3145.20" dealcurr="UAH" dealamtcurr="3145.20" dealamtexp="3145.20" dealdaysexp="27" DLFLSTAT="[1] - open" 
  DealDateCalc="30.09.2017" banktype="MFO" DealDS="04.08.2017" DealAmountPaym="3145.20" DLDPF="03.09.2017" IDFlag="2" 
  remark="Overdue for 27 days on loan 236083, date of event 10/19/2017 10:18:12, tel 0445048422" />
</doc>

Response params

iddone

Trigger ID

donedate

Effective date

idtr

Trigger ID

inn

TIN

FIOua

Full name in Ukrainian

FIOru

Full name in Russian

dealreference

Credit reference

fio

Full name ua/Full name ru

db

Date of birth

typecredit

Type of credit

dealamount

Loan amount

dealcurr

Currency

dealamtcurr

Amount of debt

dealamtexp

Overdue amount

dealdaysexp

Number of overdue days

DLFLSTAT

Agreement status

DealDateCalc

Information update date

banktype

Partner type

DealDS

Agreement start date

DealAmountPaym

Amount of compulsory payment

DLDPF

Planned contract closing date

IDFlag

Description

remark

Note

DLAMTLIM

Credit limit

...

See also in this section

Monitoring service 2.0

...

Introduction

Authorization

Receiving information

Providing information

Monitoring

Testing environment

References

...