REST API
Full CRUD for trailers, appointments, inventory, billing, carriers, users. JSON responses. Pagination. Filter and sort on every collection.
WebSocket Events
TRAILER_CHECKED_IN, DOCK_FREED, DWELL_WARNING, DETENTION_ALERT, ONE_PREDICTION — push to every connected client in under 50ms.
Webhooks
Configure HTTP callbacks for any event type. Retry with exponential backoff. Signature verification. Delivery logs.
RBAC
Role-based access: admin, supervisor, dock worker, driver, carrier, read-only. Per-endpoint permission control. Org-scoped tokens.
Rate Limiting
Per-token rate limits on REST and WebSocket. 100 msg/min per WS client. 429 responses with retry-after headers.
EDI Support
856 (Ship Notice), 214 (Shipment Status), 204 (Load Tender), 990 (Response). Transforms to/from OMNIS data model.
Every connection authenticated. Every message signed.
Every WebSocket connection is JWT-authenticated on upgrade — tokens validated from query string or Authorization header before the connection is accepted. Every outbound message is signed with HMAC-SHA256 so clients can verify it originated from OMNIS. Connections run over WSS (TLS 1.3). Rate limiting at 100 messages/minute prevents flood attacks. Broadcasts are org-scoped — your data never leaks to other tenants. Unauthenticated clients get guest access with restricted permissions.
Built API-First for Integration Partners
OMNIS isn’t a closed system. Every operation that happens in the platform — trailer check-in, door assignment, inventory scan, billing event, yard move — is an API call under the hood. The same endpoints that power the internal UI are available to integration partners, TMS providers, and custom automation workflows.
WebSocket connections are secured at every layer. JWT authentication on the upgrade handshake validates tokens before accepting connections — unauthenticated clients get guest access with restricted event visibility. Every outbound message is signed with HMAC-SHA256 using a server-side key, allowing clients to cryptographically verify that messages originated from OMNIS. Rate limiting at 100 messages per minute per client prevents denial-of-service attacks. And org-scoped broadcasts ensure that detection events, dock updates, and billing notifications only reach clients belonging to the same organization.
For systems that can’t maintain persistent connections, webhooks deliver events via HTTP POST with configurable retry logic, exponential backoff, HMAC signature verification, and delivery logging. Configure callbacks for any event type: detention alerts to your TMS, check-in notifications to your carrier’s system, billing events to your accounting platform.
EDI support covers the core logistics transaction sets: 856 (Ship Notice/Manifest), 214 (Shipment Status), 204 (Motor Carrier Load Tender), and 990 (Response to Load Tender). OMNIS transforms EDI documents to and from its internal data model, so legacy TMS and carrier systems integrate without custom development.
Your systems stay in sync. Automatically.
Configure HTTP POST callbacks for any event: trailer check-in, door assignment, detention alert, billing event, inventory scan. Every webhook includes HMAC-SHA256 signature verification, configurable retry with exponential backoff (3 attempts), and a delivery log with response codes. Integrate your TMS, ERP, or custom automation without polling.
Ready to see the OMNIS API in action?
Book a live demo and see every feature running on real warehouse data.