/moex/securities

POST /api/moex/securities

Price: 1 credit

Get Moscow Exchange security reference data by ticker or ISIN

How to use it

Get reference data for a Moscow Exchange (MOEX) security by its ticker (SECID, e.g. 'SBER') or ISIN code (e.g. 'RU0009029540'). Works for shares, bonds, ETFs, depositary receipts, indices, currencies and futures. Returns names (short/full/English), ISIN, registration number, issuer id, issue size, face value and currency, issue date, listing level, security type and group (with human-readable labels), qualified-investor flag, trading-session availability (morning/evening/weekend), and the full list of boards the security trades on with their date ranges. For bonds it additionally returns maturity date, coupon details (percent, value, frequency, next coupon date), days to redemption, initial face value, bond type/subtype and default/prospectus flags.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• security string required — Security identifier — ticker (SECID) or ISIN code (examples: "SBER", "GAZP", "RU0009029540"; minLength: 1)
• language string — Language for localized text fields (default: "ru"; one of: "ru", "en")

Response

• @type string (default: "MoexSecurity")
• secid string required
• short_name string nullable
• name string nullable
• latin_name string nullable
• issue_name string nullable
• isin string nullable
• regnumber string nullable
• issue_size integer nullable
• face_value number nullable
• face_unit string nullable
• issue_date string nullable
• listing_level integer nullable
• type string nullable
• type_name string nullable
• group string nullable
• group_name string nullable
• emitter_id integer nullable
• is_for_qualified_investors boolean (default: false)
• has_morning_session boolean (default: false)
• has_evening_session boolean (default: false)
• has_weekend_session boolean (default: false)
• maturity_date string nullable
• coupon_date string nullable
• coupon_percent number nullable
• coupon_value number nullable
• coupon_frequency integer nullable
• days_to_redemption integer nullable
• initial_face_value number nullable
• bond_type string nullable
• bond_subtype string nullable
• has_default boolean (default: false)
• has_technical_default boolean (default: false)
• has_prospectus boolean (default: false)
• boards array (default: [])
  • @type string (default: "MoexSecurityBoard")
  • board_id string required
  • market string nullable
  • engine string nullable
  • is_traded boolean (default: false)
  • is_primary boolean (default: false)
  • currency string nullable
  • history_from string nullable
  • history_till string nullable
  • listed_from string nullable
  • listed_till 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 — Security not found 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.