Product

Integration Framework

Connect Transportial to any external system (ERPs, telematics, ordering platforms, and more) with a full REST API and App Store.

REST APIOpenAPIFTPEDIApp StoreSDKKafka
REST
Full OpenAPI spec
FTP
Embedded server
EDI
File parsing
App Store
UI extensions

Modern logistics operations run on multiple systems. Transportial is designed to be connected. A full REST API with OpenAPI documentation, an embedded FTP server for legacy integrations, EDI file parsing, and an App Store for extending the UI. Every integration scenario is covered.

Key highlights

  • REST API with OpenAPI 3.0: Every entity in Transportial is accessible via a fully documented REST API with a Swagger UI for exploration and testing.
  • API key authentication: Create multiple API keys with different scopes and per-key rate limits. Each key can be assigned to a specific integration consumer.
  • Embedded FTP server: For legacy systems that only support file-based integration, Transportial includes an embedded FTP server.
  • EDI file parsing: Standard freight EDI formats (EDIFACT, X12) are parsed and converted to Transportial transport orders and consignments automatically.
  • Integration pipeline: A structured processing pipeline with queue management, retry logic, dead-letter queuing, status tracking, and error alerting.
  • App Store: Third-party developers can build and publish apps to the Transportial App Store. Apps can embed custom UI panels using the App Store SDK.
Technical details

The integration pipeline is backed by Apache Kafka for reliable message delivery. API requests are rate-limited per key using a sliding window algorithm. App Store apps run in sandboxed iframes with a defined message-passing API.

Ready to put this to work?

Start free with full platform access, or talk to our team about your specific operation.