AAdminyraeFTIEarly access
eFTI API

Put eFTI behind a stable API instead of inside your TMS.

Adminyra is building a transport-software-facing API that turns eFTI platform concepts into predictable application resources while the underlying regulatory and interoperability layers remain isolated.

See TMS integrationSandbox
Adminyra eFTI
TMS / ERP / logistics software
↓
Adminyra eFTI platform
↓
eFTI Gate / regulated exchange
REST-orientedTenant-awareVersioned CMDSSandbox-first
01

A practical application boundary

The API starts with the eFTI consignment movement data set as the regulatory resource attached to a freight movement. Data can be created, validated, versioned and prepared for controlled authority access.

Gate protocols and formal certification stay behind this boundary so an integrated TMS does not need to redesign its own API client whenever the interoperability layer changes.

  • Create and retrieve CMDS resources
  • Produce immutable dataset versions
  • Associate applicable eFTI data subsets
  • Maintain per-element audit history
02

Sandbox and production stay separate

Sandbox proves mapping, validation and workflow behaviour without pretending that test data is certified production exchange.

Production Gate functions remain restricted until the relevant interoperability and certification requirements are satisfied.

FAQ

Practical questions about eFTI API

Is Adminyra already a certified eFTI platform?

No. Adminyra eFTI is under active development. Production authority exchange stays disabled until the required interoperability, conformity-assessment and certification steps are complete.

Can we integrate before production certification?

Yes. Data mapping, sandbox API work, CMDS lifecycle design and application integration can be prepared before production Gate trust is enabled.

Can one TMS integration serve multiple customers?

Yes. The architecture is multi-tenant so a software provider can integrate once while organisations, datasets, rights and audit trails remain separated.

Primary sources

Official EU material behind this page

Official sourceImplementing Regulation (EU) 2025/2243Open source ↗Official sourceDelegated Regulation (EU) 2024/2024Open source ↗
Continue exploring

Related eFTI topics

TMS integrationTMS eFTI Integration

Connect a transport management system to eFTI infrastructure without rebuilding the TMS. Map shipment data, create CMDS resources and manage regulatory exchange through an API.

Read more →Consignment Movement Data SeteFTI CMDS

What an eFTI CMDS is and how it relates to a consignment movement, data subsets, versions and the platform lifecycle.

Read more →Developer sandboxeFTI Sandbox

Test eFTI CMDS creation, mapping, UIL workflows and TMS integration in a non-production sandbox before certification and live Gate connectivity.

Read more →
Build before the rush

Prepare the integration before 9 July 2027.

Start with a real freight-data mapping in the sandbox. Production Gate exchange remains locked until the certification and interoperability path is complete.

Explore early accessOpen sandbox