See turnover and account transactions from Alfa-Bank in chat

The agent calls the Alfa-Business API at baas.alfabank.ru and starts from the list of company accounts — the same request that verifies the connection. From there it pulls the statement for the selected accounts over a period, totals incoming and outgoing turnover, surfaces large and unusual transactions and breaks payments and receipts down by counterparty and purpose, so the weekly summary comes together without a manual export from the internet bank.

A bank statement is not the same thing as what is happening on the account right now: it carries the transactions the bank has already posted, so a fresh payment or credit appears in it later than the company learns about it. The agent works from the posting date rather than the moment the payment became known, and when reconciling against 1C entries it matches transactions by amount, date and counterparty details rather than by the payment purpose alone.

By default the agent reads: accounts, statements, transaction history, reconciliation with the books and recurring summaries. The payment part of the API is available, but signing an order stays on the bank's side and goes through confirmation in Alfa-Business Online — the agent cannot send money silently. Before any write action it shows the details and the amount it has assembled and stops until you confirm them.

Access has two layers: the API key travels as a token, while some methods additionally require a client certificate, so the set of available operations depends on which layer is open. The statement comes back in pages and with a cap on the length of the period, so the agent collects long intervals in chunks and stitches them together itself, holding the request rate. If there is no data for the period or the key lacks permissions, it says so directly instead of showing an empty table.