/sbis/contragents/search

POST /api/sbis/contragents/search

Price: 5 credits

Search Russian companies and sole proprietors (contractors) by name, INN, OGRN or other requisites. Returns a list with name, INN/KPP/OGRN/OKPO, region, category, address, registration date, revenue, director and primary activity code. Supports region and industry-category filtering and ordering by relevance or revenue.

How to use it

Search Russian legal entities and sole proprietors by free-text query (name, INN, OGRN or requisites). Each item has id, inn, kpp, ogrn, okpo, name, region, category, address, registered_at, revenue, director and main_activity_code. Optional region codes filter, industry category filter and sort (relevance or revenue).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search query — company name, INN, OGRN or other requisites (examples: "газпром", "7707083893", "1027700132195"; minLength: 1)
• count integer required — Number of contractors to return (min: 1)
• region array — Optional list of Russian region codes to filter by (e.g. 77 for Moscow) (default: []; examples: ["77"])
• category array — Optional list of industry categories to filter by (default: []; one of: "auto_service", "security", "business_finance", "paper_packaging", "woodworking", "computers_software", "beauty_health", "light_industry", "machinery", "medicine_pharma", "metals", "science_education", "real_estate", "office_home", "logistics", "printing_advertising", "food_beverages_tobacco", "retail", "communications", "agriculture", "sport_leisure_tourism", "construction_materials", "construction", "raw_materials", "fuel_energy", "transport", "services", "chemical_industry", "ecology_cleaning", "electrical", "undefined"; examples: ["business_finance"])
• sort string — Result ordering (default: "relevance"; one of: "relevance", "revenue")

Response

• @type string (default: "SbisSearchItem")
• id string required
• spp_id integer nullable
• is_sole_proprietor boolean (default: false)
• name string nullable
• inn string nullable
• kpp string nullable
• ogrn string nullable
• okpo string nullable
• region string nullable
• category string nullable
• address string nullable
• registered_at string nullable
• revenue integer nullable
• main_activity_code string nullable
• uuid string nullable
• director object nullable
  • @type string (default: "SbisPerson")
  • name string nullable
  • role string nullable
  • since_at string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.