Keep Kaspi orders under control right in the chat

The agent works with the shop through Shop API v2 — the same interface that sits behind the Kaspi.kz seller account. It reads orders and their entries, product cards, reviews, cities and pickup points, and counts amounts in tenge, exactly as they come from the Kazakh account. Sales are aggregated by product and period, orders by status, and what you get back is an analysis rather than an export you then have to open in a spreadsheet.

The data here is built in three steps: an order itself carries no list of goods — the agent first fetches its entries, and from every entry moves on to the product card. So the question of what exactly was bought over the week costs several passes, and the agent walks them page by page instead of trying to pull everything in one request. The order state filter is applied on the Kaspi side, so the archive is not dragged along for the sake of recent deals.

Kaspi sends no notifications, so the agent sees new and stuck orders at the moment you ask or when it checks them on a schedule. Before calling an order a problem, it re-reads the current state — a status in Kaspi changes faster than the previous summary manages to go stale. Replies to reviews the agent prepares as text and shows to you: publishing them stays your step in the account.

The token travels in a header of its own, with no OAuth and no sign-in under your account, and it can be revoked at any moment, which cuts the agent off instantly. The agent sees exactly the shop the token belongs to — someone else's order will not come back by number. Selections run page by page with the date filter applied on the Kaspi side, so a long period never turns into one unliftable export. The agent holds the request rate itself, and if a section is empty or the token has been revoked it says so directly instead of showing an empty table.