Calculate CDEK delivery prices and transit times in chat

The agent calls the CDEK API at api.cdek.ru: it calculates the cost and transit time for a route, weight and dimensions, pulls up the reference lists of regions, cities and pickup points, reads orders along with their status history and collects print forms and photos once they are ready. A pickup point is chosen not by city alone but with an eye on parcel dimensions and the opening hours of the point — otherwise the customer arrives at a closed door.

Delivery statuses do not arrive on a schedule and polling an order in circles is pointless, so CDEK sends the events itself: an order status change, a print form ready and a photo ready. The agent catches them over a webhook, ties them to the CDEK order number and, from the accumulated history, sees which parcel has been sitting on one status longer than usual — that is, stuck rather than simply in transit.

On the write side the agent does exactly two things: create a delivery order and book a courier. It shows both to you before sending — route, dimensions, recipient, pickup date — and takes the step only after confirmation, because a mistake here costs a real trip and real money. Once the order is created the agent returns the tracking number and follows the parcel read-only from there.

The connector obtains and refreshes the token on its own, so the keys are entered once and can be forgotten afterwards. The request rate is held within five per second: a bulk tariff calculation is split into batches, and cities are taken from the CDEK reference list rather than from the text of a request, or the address will not match. About data missing from a response the agent says so directly instead of showing an empty table.