Product
Integration Framework
Connect Transportial to any external system (ERPs, telematics, ordering platforms, and more) with a full REST API and App Store.
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.
How it works
Pick the integration type
Start from a preset connector for common telematics and logistics systems, a self-configurable integration for anything with an API or file interface, direct API access for your own developers, or a file template for recurring spreadsheets.
Configure the connection
Set the endpoint, polling schedule or trigger event, and authentication: API keys, basic auth or custom headers. Inbound file flows can use the embedded FTP server instead, so legacy systems just drop a file.
Map the data visually
Pair each incoming field with a field on the Transportial data model in the visual mapping editor, including nested structures like stops and goods lines. No scripting is required, and AI-generated mapping suggestions get you most of the way in one click.
Test and activate
Run the integration against real sample data, inspect the resulting orders or updates, then switch it on. Every run is logged so you can see exactly what came in and what was created.
Monitor the pipeline
The integration pipeline queues, retries and dead-letters failed messages, and can alert you when something needs attention. Failures are visible and re-playable, never silent.
Preset connectors and self-built integrations, one framework
Most platforms make you choose between a fixed catalogue of connectors and an expensive custom project. Transportial treats both as the same thing: a preset integration is simply a pre-filled configuration of the same framework you can configure yourself. Presets exist for common board computers, telematics providers and port community systems, and each one exposes its settings, so you can adjust polling intervals, enabled functions or credentials without waiting for a vendor.
When there is no preset, the self-configurable integration builder covers systems that speak HTTP, files or FTP. You define the endpoint or file drop, the schedule or triggering event, and the authentication, then map the payload onto Transportial's data model. Because orders, trips and consignments follow the OTM5 open standard internally, a mapping built once keeps working as the platform evolves, and the same order data can flow out to any partner that understands the standard.
For everything else there is the REST API, documented with OpenAPI 3.0 and browsable through Swagger. Every entity you see in the interface, from transport orders to invoices to vehicles, is available over the same API the product itself uses, so an integration can do anything a user can do.
Built for the messy reality of logistics data
Logistics integration is rarely clean JSON over HTTPS. A customer sends orders as a spreadsheet every morning, a partner's ERP only exports EDIFACT, an older warehouse system can only upload to FTP. Transportial covers these paths natively: an embedded FTP server accepts file drops and processes them automatically, standard freight EDI formats such as EDIFACT and X12 are parsed into transport orders without custom scripting, and file templates turn recurring spreadsheets into structured orders.
Incoming data is also rarely consistent. Field names arrive in different languages, addresses are split differently, references live in odd columns. The visual mapping editor is built for exactly this: you see the real incoming fields next to the target model and connect them directly, including into nested structures like the second stop of the first consignment. The AI mapping generator reads a sample payload and proposes the full mapping, which you review and adjust rather than build from scratch.
Failures you can see, not tickets you discover later
The most expensive integration failure is the silent one: an order that never arrived, discovered when the customer calls. Transportial's integration pipeline is queue-based, with retry logic for transient errors and a dead-letter queue for messages that repeatedly fail. Each message carries its processing status, so a stuck order is a visible item you can inspect and replay, not an absence you have to notice.
Assertions and failure notifications can be attached to integrations, so the right person is told when a feed goes quiet or a payload stops matching expectations. Combined with per-key API rate limits and scoped API keys, one misbehaving integration stays contained: you can throttle or revoke a single consumer without touching the rest.
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.
Frequently asked questions
Can Transportial integrate with our existing ERP or TMS?
Yes. If the system exposes an API or can exchange files, it can be connected through a self-configurable integration, the REST API, the embedded FTP server or EDI parsing. Common telematics and logistics systems are available as presets that only need credentials.
Do we need developers to build an integration?
Not for most cases. Preset connectors and the visual data-mapping editor are designed for operational teams: you configure the connection and pair fields on screen. Developer involvement is only needed when you want to build against the REST API directly or publish an App Store app.
What happens when an integration fails?
Failed messages are retried automatically, and messages that keep failing land in a dead-letter queue with their error and payload preserved. You can inspect, fix and replay them, and configure notifications so failures alert the right person instead of surfacing weeks later.
Which EDI formats are supported?
Standard freight EDI formats, including EDIFACT and X12, are parsed and converted into Transportial transport orders and consignments automatically. Custom or partner-specific file layouts can be handled with file templates and the mapping editor.
Is there an API rate limit?
Rate limits are configured per API key rather than per account. You can create multiple keys with different scopes and limits, assign one to each consuming system, and revoke or throttle a single key without affecting other integrations.
Can we extend the Transportial interface itself?
Yes. The App Store lets third-party developers publish apps that embed custom panels inside the dashboard, trip views and order pages through a sandboxed SDK, so you can add functionality without modifying or forking the core product.
View all features
Transport Order ManagementInteractive Plan BoardAI-Powered Trip OptimisationFleet & Resource Management3D Load PlanningOpenMove Driver AppReal-Time Vehicle TrackingMulti-Modal RoutingPricing EngineInvoicing & Financial ManagementMessage AutomationsDocument Management & GenerationIntegrated Email InboxIn-App ChatCustomer & Business PortalIntegration FrameworkReporting & InsightsMulti-Tenancy & White-LabelSecurity & Access Control
Ready to put this to work?
Start free with full platform access, or talk to our team about your specific operation.