Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ShohjahonSohibov/repo-for-agent/llms.txt

Use this file to discover all available pages before exploring further.

UpdaterAgent is a Transportation Management System (TMS) backend built with .NET 8 and Clean Architecture. It serves as the central operations hub for freight logistics — managing the full load lifecycle, tracking real-time ELD positions, routing driver notifications, and integrating with external platforms including QuickManage, Samsara, Zippy, Google Maps, and Telegram. This page explains what the system does, how it is structured, and where to go next.

​
Key features

Load management

Full lifecycle tracking from Upcoming through Dispatched, InTransit, and Delivered. Includes multi-stop routing, driver assignment with forward-fill logic, ETA calculation, delay detection, and document management for BOL, POD, and rate confirmations.

ELD tracking

Real-time vehicle position imports from Zippy, Samsara, and UTrackin every 25 minutes. Includes stationary driver detection, sleep timer monitoring, and position-based ETA updates.

External integrations

Webhook and REST integrations with QuickManage TMS, Nylas email, Telegram Bot, Google Maps, OSRM, Nominatim, and AskAI for automated load imports, routing, geocoding, and AI document analysis.

Multi-tenancy

Automatic row-level tenant isolation via EF Core global query filters. All entities carry a TenantId; no manual .Where(x => x.TenantId == ...) filtering is required in application code.

​
Technology stack

UpdaterAgent is built on the following technologies:
LayerTechnology
Backend framework.NET 8, ASP.NET Core
DatabasePostgreSQL 16
ORMEntity Framework Core 8 (Npgsql), Dapper
Background jobsHangfire (11 recurring jobs)
Real-time communicationSignalR
LoggingSerilog, Grafana Loki
API documentationSwagger / OpenAPI
The API surface spans 41 REST controllers with 200+ endpoints. Interactive documentation is available at https://localhost:5001/swagger when running locally.

​
Clean Architecture layers

The codebase is organized into four layers with a strict inward dependency flow: Api → Application → Infrastructure ← Domain. 
src/
├── UpdaterAgent.Api            → Controllers, middleware, SignalR hubs
├── UpdaterAgent.Application    → Services, background jobs, DTOs, business logic
├── UpdaterAgent.Infrastructure → EF Core, external brokers, persistence
└── UpdaterAgent.Domain         → Entities, enums, interfaces (zero dependencies)
The Domain layer has zero external dependencies. All entities use AuditableModelBase<long> and implement ITenantEntity for automatic audit trails and tenant isolation.

​
Security model

Authentication uses JWT with refresh tokens. Authorization is permission-based. Webhook security uses HMAC signature verification for QuickManage inbound events. All external communication is encrypted over HTTPS.
The IgnoreQueryFilters() method bypasses the global tenant filter. It is permitted only for login flows (no JWT yet) and cross-tenant admin operations. Always re-add the soft-delete check: .IgnoreQueryFilters().Where(x => !x.IsDeleted).

​
Where to go next

Architecture

Understand the Clean Architecture layers, dependency flow, and design decisions.

API Reference

Explore authentication, endpoint schemas, and request/response examples.

Quickstart

Clone the repo, apply migrations, and make your first authenticated API call.

Build docs developers (and LLMs) love

Get started for freeTalk to us