Supplier Check in RNP

The “Supplier Check in RNP” endpoint allows you to retrieve information about a supplier’s presence in the Register of Unscrupulous Suppliers (RNP) using their INN (Taxpayer Identification Number).

Endpoint

GET https://api-v2.multitender.ru/rnp/check-supplier

Request Parameters

Parameter Name	Required	Description
`supplierINN`	Yes	Supplier’s INN
`apikey`	Yes	Your API key
`format`	No	Response format (`xml` or `json`). Default: `xml`

Request Examples

Check supplier by INN

https://api-v2.multitender.ru/rnp/check-supplier?supplierInn=7707083893&apikey=.....

Check with JSON response format

https://api-v2.multitender.ru/rnp/check-supplier?supplierInn=7707083893&format=json&apikey=.....

Response Structure

The response contains information about the supplier’s presence in the RNP. The structure differs slightly between XML and JSON formats.

XML
JSON

<response>
  <supplierINN>7707083893</supplierINN>
  <supplierName>LLC "COMPANY"</supplierName>
  <inRNP>true</inRNP>
  <entries>
    <entry>
      <registrationNumber>RNP-0001234-01/2024</registrationNumber>
      <registrationDate>2024-01-15</registrationDate>
      <reason>Improper fulfillment of contract obligations</reason>
      <contractNumber>0373100001223000123</contractNumber>
      <excludeDate>2026-01-15</excludeDate>
      <federalLaw>44-FZ</federalLaw>
      <customerName>CITY ADMINISTRATION</customerName>
      <customerINN>7701234567</customerINN>
    </entry>
  </entries>
</response>

{
  "supplierINN": "7707083893",
  "supplierName": "LLC \"COMPANY\"",
  "inRNP": true,
  "entries": [
    {
      "registrationNumber": "RNP-0001234-01/2024",
      "registrationDate": "2024-01-15",
      "reason": "Improper fulfillment of contract obligations",
      "contractNumber": "0373100001223000123",
      "excludeDate": "2026-01-15",
      "federalLaw": "44-FZ",
      "customerName": "CITY ADMINISTRATION",
      "customerINN": "7701234567"
    }
  ]
}

<response>
  <supplierINN>7707083893</supplierINN>
  <supplierName>LLC "COMPANY"</supplierName>
  <inRNP>false</inRNP>
  <entries/>
</response>

{
  "supplierINN": "7707083893",
  "supplierName": "LLC \"COMPANY\"",
  "inRNP": false,
  "entries": []
}

Response Fields Description

Field	Type	Description
`supplierINN`	string	Supplier’s INN
`supplierName`	string	Supplier’s name
`inRNP`	boolean	Whether the supplier is in the RNP
`entries`	array	List of RNP entries
`entries[].registrationNumber`	string	RNP entry registration number
`entries[].registrationDate`	date	Date of inclusion in RNP
`entries[].reason`	string	Reason for inclusion in RNP
`entries[].contractNumber`	string	Contract number where violation occurred
`entries[].excludeDate`	date	Date of exclusion from RNP
`entries[].federalLaw`	string	Federal law (44-FZ, 223-FZ, etc.)
`entries[].customerName`	string	Customer’s name
`entries[].customerINN`	string	Customer’s INN

Error Codes

Code	Description
`400`	Invalid request parameters
`401`	Invalid or missing API key
`404`	Supplier not found
`429`	Rate limit exceeded
`500`	Internal server error

Notes

RNP data is updated daily
A supplier may have multiple entries in the RNP simultaneously
After the expiration date (excludeDate), the entry is automatically removed from the register
Presence in the RNP may serve as grounds for rejecting a bid to participate in a procurement

Multitender.ru