Check marking codes in batches without opening GIS MT

The agent calls the GIS MT True API at markirovka.crpt.ru: it runs marking codes through in batches and reads their statuses, pulls the list of turnover documents, looks up product cards by GTIN in the national catalogue and reconciles balances against warehouse stock by product group. From that it works out which codes are in circulation, which have been retired and which have not entered circulation yet, and where your own stock records diverge from the marking system.

Accepting a document and processing it are two different events in GIS MT: the system takes a shipment or an acceptance immediately, the outcome shows up later, and some documents settle as unprocessed or rejected with an error. The agent keeps those states apart and reports not the fact of submission but the actual fate of the document. It treats code statuses with the same caution: retirement is recorded through cash register receipts and does not reach the system instantly.

The agent barely writes anything here, and that is a property of the system itself: submitting documents into circulation is confirmed with a qualified electronic signature created by your own token, not by the agent. So it gathers data, finds discrepancies and prepares lists ready for signing — checked codes, stalled and rejected documents, cards missing mandatory attributes for their product group — and signing and sending stays your decision.

Codes are checked in batches of several hundred per request: asking one by one would run straight into the rate limit, while a batch comes back as a single list that shows at once which codes the system does not know at all. Once the token's lifetime runs out, requests return an authorisation error and the agent says so outright instead of retrying in silence. It sees exactly the product groups open to your organisation, and when data is missing it says so rather than showing an empty table.