taxiCRM
Connect taxiCRM to the AI agent: drivers, trips, shifts, balances, payouts and fines
Connect taxiCRM to the AI agent: drivers, trips, shifts, balances, payouts and fines. The agent reconciles shifts with transactions and spots negative balances.
DocumentationВ минусе 17 водителей из 143, суммарно −86 400 ₽.
Свёл смены, поездки и транзакции за неделю по двум кабинетам агрегаторов. У 11 из них минус закрывают неоплаченные штрафы, ещё у четверых договор аренды стоит на паузе вторую неделю.
Integration scenarios
Driver balances before payout
The agent reconciles shifts, trips and transactions and shows which drivers went negative and what balance each one brings into the payout.
Fines and rental agreements
The agent collects unpaid fines and paused rental agreements and links them to specific cars and drivers in the fleet.
Morning fleet summary
Every morning the agent sends yesterday totals: trips, shifts and driver transactions broken down by aggregator cabinets.
Review of driver conversations
The agent goes through fleet chats, collects driver requests left without a reply and shows which questions come up most often.
How to connect
Open your fleet cabinet and note the subdomain
The cabinet address looks like https://yourfleet.taxicrm.ru — the part before .taxicrm.ru is the subdomain. The public API lives at the same address; there is no separate API domain.
Open «Компания» → «Настройки компании» → «API»
In taxiCRM the section «Компания» → «Настройки компании» → «API» (Company → Company settings → API) holds the fleet API key: every request is signed with it — sha1 of body plus key, 40 hex chars in Authorization.
Copy the fleet API key
One key covers the whole fleet and opens all of its data — drivers, trips, shifts, payouts, penalties, rentals. Treat it as a password: requests signed with it act on the fleet's behalf.
Ask taxiCRM support to open the payout methods
Per the spec, driver payout, balance change and payout-block change are granted only on request through taxiCRM support. Without it those three methods answer 402; reading data works right away.
What the agent does in the first 10 minutes
- Will total shifts and trips to show which drivers went negative and what balance each has before payout
- Will pull unpaid penalties and paused rental contracts and match them to specific cars and drivers
- Will send a morning digest of yesterday: trips, payouts and driver transactions broken down by aggregator cabinet
FAQ
How do I connect taxiCRM?
With the fleet subdomain and API key: the subdomain is the part of your cabinet address before .taxicrm.ru, and the key sits under Company → Company settings → API. The connector signs the request itself, so you do not need to pass a signature.
What does the agent see in taxiCRM?
Drivers and their balances, trips, shifts, transactions, payouts and payment details, cars and rental agreements, fines, driver chats and the fleet CRM pipelines.
Does the agent write to taxiCRM?
It can: register drivers, create deals and cars, pause a rental and message a driver in chat. By default it works in read and summary mode.
Why do some methods answer 402?
Paying out a driver, changing a balance and unblocking a transaction are opened only on request to taxiCRM support, as the spec states. Reading data works right after you connect.
