When your carrier is booked in the TMS for a specific day, Docklyx receives the inbound webhook, validates the payload and creates the appointment. While that truck moves through your yard, Docklyx sends outbound events to your WMS so inventory, dock and labor systems know what just happened.
Inbound creates the appointment from your source system. Outbound keeps WMS, ERP and BI updated as the truck moves.
The integration layer has one job: accept trusted operational intent from your systems, then report every verified yard event back out with enough context for downstream systems to act.
A TMS or ERP posts a booking request to Docklyx.
Signature, site, carrier, date and event type are validated before processing.
Docklyx creates or updates the appointment and keeps the external reference.
As the truck moves, signed events are sent to subscribed WMS or BI endpoints.
Retryable failures continue with backoff while admins see the health state.
Timeout · HTTP 429 · temporary 5xx
After repeated failures, Docklyx can pause the subscription until the endpoint is fixed.
Dead letter · invalid endpoint · repeated 4xx
Your TMS sends the carrier, date, load type, PO or reference and preferred dock window. Docklyx validates the payload and creates the appointment in the right DC.
Check-in, yard assignment, dock arrival, operation start, checkout, cancellation and exception events can be sent to your WMS, ERP or data warehouse.
Payloads use HMAC-SHA256 signatures and raw-body verification. Secrets are shown once, can be rotated, and every endpoint is protected against unsafe targets.
Temporary failures stay pending with exponential backoff. Repeated failures move to dead letter, notify admins and can be replayed after the endpoint is fixed.
External references, dock codes, carrier names and site IDs map into Docklyx without forcing your TMS or WMS to change its vocabulary.
Supported events, example payloads and signature examples live beside delivery history, so teams can debug without chasing a PDF.
One truck, two systems, no manual bridge between them.
Your TMS schedules Norte Rapido for May 18 at DC Bajio.
Docklyx validates signature, maps the DC and creates the appointment.
The appointment behaves like any native Docklyx booking.
Guard scans the QR. Docklyx emits checkin.completed.
Zone assignment event is sent to WMS with appointment and carrier references.
dock.status_changed and appointment.updated keep downstream systems current.
checkout.completed carries gate-to-gate timing for WMS and BI.
If your endpoint failed, admins inspect response body and replay the event.
A booking created in your TMS does not need to be typed again into Docklyx.
Yard and dock events leave Docklyx as soon as the operational state changes.
Temporary failures retry automatically before moving to dead letter.
Every outbound event has payload, status, response and replay history.
If it's not here, sales replies same-day — not a form into the void.
Monthly or annual billing (save 17%).
21 days free · No credit card required · 1-day setup
We map one inbound booking event and one outbound yard event first. Then we expand the catalog once your team trusts the flow.