01
Generic API brochures
Endpoint lists that do not match what the dispatch desk actually writes on a live trip.
Logistics APIs · Available
Connect transportation data to your systems.
Integrate trip, fleet, and visibility data from ZAFTYS TMS with ERP, warehouse, and commercial workflows. We only discuss endpoints that are implemented. Scope is confirmed in enterprise onboarding.
Available
The integration problem
ERP cannot invent a trip the TMS never held
Finance and planning systems need clean movement data. Middleware promises fail when the operational record is incomplete or undocumented.
02
Manual rekey into ERP
Billing and status copied by hand because trip truth never left the TMS.
03
Unscoped onboarding
Integration projects that start without stating which modules and events are live.
What you get
APIs around real dispatch workflows
Built for shippers and operators already on ZAFTYS TMS, not a standalone middleware brand.
01
Trip data for downstream systems
Operational records available for integration where your commercial stack needs the movement.
02
Status events where supported
Event-driven updates for dispatch and delivery milestones that exist in the product today.
03
Fleet and document context
Connect registry and compliance fields when the onboarding scope includes fleet modules.
04
Enterprise onboarding
Structured planning for which systems, corridors, and users come online first.
05
Honest endpoint boundaries
We do not advertise APIs that are not implemented. Scope is written before build work starts.
06
Same internal platform
Integrations sit on the stack ZAFTYS uses for its own contracted trips.
Product
Operational data from the TMS spine
APIs only matter when Command Center, Shipments, and close-out already hold the trip.
app.zaftys.com
app.zaftys.com
Who it is for
IT and ops leads connecting commercial systems
01
IT and integration leads
Need scoped endpoints and onboarding, not a PDF of aspirational APIs.
02
Shipper technology teams
Want trip and ePOD data into ERP or planning tools after TMS is live.
03
Fleet operator systems owners
Connecting dispatch truth to billing and internal reporting stacks.
How we onboard
Scope first. Then endpoints.
API work starts with which trip events and systems matter. We do not start from a generic swagger dump.
- Discuss specific endpoints during enterprise onboarding
- Built around dispatch workflows, not generic middleware
- Availability varies by module and customer program
- TMS login and desk process come before integration theatre
Availability
Available
Available under scoped enterprise onboarding
Logistics APIs are offered where implemented for your program. This page does not publish a fake universal endpoint catalog. Ask for the live scope before you plan an ERP project.
Scope the integration against trips you actually run
Tell us which systems must receive trip and ePOD data. We will confirm what is live before anyone writes middleware.