/sbis/contragents

POST /api/sbis/contragents

Price: 10 credits

Get a Russian company or sole proprietor (contractor) by INN, OGRN or company profile URL: short and full legal name, INN/KPP/OGRN/OKPO/OKTMO, Pension Fund / Social Insurance registration numbers, registration date, legal address, annual revenue, charter capital, director, primary activity (OKVED), branch addresses, section counters, company rating and employer rating.

How to use it

Fetch a single Russian legal entity or sole proprietor by INN (10/12 digits), OGRN (13/15 digits) or a full company profile URL. Returns one item with name, full_name, inn, kpp, ogrn, okpo, oktmo, pfr_number, fss_number, sfr_number, registered_at, address, postal_code, locality, revenue, charter_capital, director, main_activity (OKVED code+name), branches, counters, rating (overall company rating) and employer_rating (rating as an employer).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• contragent string required — Company INN (10 digits for a legal entity, 12 for a sole proprietor), OGRN (13 digits for a legal entity, 15 for a sole proprietor), or a full company profile URL (examples: "7707083893", "1027700132195", "https://saby.ru/profile/7707083893-773601001"; minLength: 1)

Response

• @type string (default: "SbisContragent")
• id string required
• url string required
• is_sole_proprietor boolean required
• name string nullable
• full_name string nullable
• inn string nullable
• kpp string nullable
• ogrn string nullable
• okpo string nullable
• oktmo string nullable
• pfr_number string nullable
• fss_number string nullable
• sfr_number string nullable
• registered_at string nullable
• address string nullable
• postal_code string nullable
• locality string nullable
• revenue integer nullable
• charter_capital integer nullable
• director object nullable
  • @type string (default: "SbisPerson")
  • name string nullable
  • role string nullable
  • since_at string nullable
• main_activity object nullable
  • @type string (default: "SbisActivity")
  • code string nullable
  • name string nullable
• branches array (default: [])
• counters object nullable
  • @type string (default: "SbisContragentCounters")
  • owner_count integer nullable
  • license_count integer nullable
  • inspection_count integer nullable
  • event_count integer nullable
  • trademark_count integer nullable
• rating object nullable
  • @type string (default: "SbisRating")
  • value number nullable
  • count integer nullable
• employer_rating object nullable
  • @type string (default: "SbisRating")
  • value number nullable
  • count integer 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 — Contractor not found (well-formed INN/OGRN but no matching record) 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.