Pull SberBusiness balances and operations together in chat

The agent calls the SberBusiness API and starts from the list of company accounts, the same request that verifies the connection. From there it works with statements, payments, the counterparty directory, corporate cards and payroll services: balances as of a date, large movements for the day, incoming and outgoing payments by counterparty for a period and a reconciliation of payroll registers against 1C:ZUP statements before the register goes to the bank.

The statement is the heaviest section of the Sber API, and its rate limit is tighter than that of the other methods. The agent accounts for that: it requests the period in portions and holds the statement rate separately from other calls, so a long report does not hit a refusal halfway through. The connection is unusual too (mutual TLS): the certificate is presented on every request, and the agent tells a dropped session apart from a rights refusal instead of lumping both into one error.

The agent prepares payments but does not send them. It assembles the document, checks the details, the amount and the counterparty against the directory and shows any discrepancies, while signing stays in SberBusiness and follows your own signature rules. Without confirmation on the bank's side no payment leaves, and the same holds for payroll registers: the agent brings them to a reconciled, ready state, and the decision to send is yours.

Access is granted over OAuth: an application whose scope includes openid exchanges the authorization code for a token and refreshes it afterwards, so there is no need to reconnect every time. That same scope defines which sections the agent can reach at all: accounts, statements, payments and payroll services are switched on separately. If there is no data for the period or the scope does not cover a section, the agent says so directly instead of showing an empty table.