Break down your T-Investments portfolio and quotes in chat

The agent calls the T-Invest API at invest-public-api.tinkoff.ru/rest and reads four domains: brokerage accounts and portfolio composition, quotes and candles for instruments, the securities reference with search by ticker, name and ISIN, and placed orders. Its first request fetches the list of accounts — without it there is no telling which portfolio to count, and one token can cover several accounts.

REST here is a wrapper over a gRPC contract: every call is a POST to a method name of the form UsersService/GetAccounts, parameters travel in the body, and the usual query strings do not exist. The portfolio comes back per account rather than as one pile, so the agent assembles the how-much-in-total summary itself, walking the accounts and adding up positions. The value in the response is the current market valuation, a snapshot at request time rather than a fixed end-of-day total.

On reading the agent is self-sufficient, on actions it is not. It places orders only if the token was issued with full access: on a read-only token the API simply will not accept them, and the agent names the reason instead of pretending it sent something. Before anything goes to the exchange it confirms the action with you separately. There is no current account, statement or payment order here — this is a brokerage account, and banking operations live in the T-Bank Business connector.

Access rests on a single T-Invest API token, and every request goes out in its name. The token lives three months from the last use — after idling the API answers with error 40003, and the agent names that reason instead of showing an empty table. Limits differ per method: reference books and quotes are generous, account operations are stricter, so history over a long period is requested in windows at around two and a half calls per second.