Introduction
eFTI TestBed is a playground for eFTI project member states. It provides an environment for testing implementations of eFTI Gate, Platform and Authority systems.
The eFTI TestBed includes:
- Gate (with Admin Panel)
- Demo Platform
- Demo Authority UI
The Gate is compliant with the eFTI regulations and compatible with the reference implementation, although it does not use the reference implementation internally.
The Demo Platform a simplified eFTI platform interface that can upload identifiers to the Gate and respond to Gate requests. It is not a fully functioning TMS system.
The Demo Authority UI provides a simple user interface for creating eFTI competent authority requests. It does not include an authority application backend.
The Admin Panel is not an official part of the eFTI Gate, but it significantly simplifies usage and integration. It provides visibility into the internal processes of the Gate.
The eFTI TestBed is available at: https://eu-ee32.eftisandbox.eu/
Onboarding
Contact support@dlk.ee to register your Gate, Platform or Authority in the eFTI TestBed.
After contacting the support email and expressing your intent to connect with the eFTI TestBed, you will receive credentials for a user account with access to the Admin Panel.
Integrations
For Gates
Since gates only communicate with each other through eDelivery, you must support the following eFTI messages via eDelivery:
The Gate’s eDelivery endpoint is: https://eu-ee32.eftisandbox.eu/services/msh.
For eDelivery integration, both parties must exchange certificates.
Make sure your Gate’s certificate is configured in the Admin Panel.
The certificate of the eFTI TestBed Gate is visible under the This gate details view.
For Platforms
As a platform you have two ways to connect with the eFTI TestBed:
You can choose either approach, but we strongly recommend the REST API since it is (a lot) faster and easier to implement. If needed, you can also use both.
Messages exchanged between the platform and the Gate must conform to the eFTI schemas.
When a consignment is created on the platform, an identifiers set should be sent to the Gate. The structure of the identifier set is defined in this XSD.
When an authority queries a consignment through the Gate, the platform must respond with the consignment dataset based on the requested subsets. The dataset structure and subset-dependent fields are defined in this XSD.
Subsets can be thought of as access rights that define which data an authority is allowed to request.
For example, if an authority has subset EU01, it can only access the data fields defined for EU01.
REST API
For REST API integration, your platform must:
- Expose two endpoints
- Send one request to the Gate
The endpoints your platform must expose are documented in this OpenAPI specification.
The Gate endpoint used by platforms is documented in this OpenAPI specification under the For Platforms section.
Authentication with REST API is done by using Basic token in the header of the request. Example of the Authorization header with email abc@example.com and pass 1234 construct the header like so:
Authorization: Basic base64Encode(abc@example.com:1234)
a.k.a
Authorization: Basic YWJjQGV4YW1wbGUuY29tOjEyMzQ=
eDelivery
For eDelivery integration, your platform must implement an eDelivery endpoint capable of handling the following eFTI messages:
Additionally, the platform must send a saveIdentifiersRequest to the Gate’s eDelivery endpoint.
Because eDelivery is asynchronous, the platform must respond to a uilQuery with a corresponding uilResponse.
The Gate’s eDelivery endpoint is: https://eu-ee32.eftisandbox.eu/services/msh.
For eDelivery integration, both parties must exchange certificates.
Make sure your Gate’s certificate is configured in the Admin Panel.
The certificate of the eFTI TestBed Gate is visible under the This gate details view.
For Authorities
Authorities can integrate with the Gate using a simple REST API. Other integration types are not currently planned for the eFTI TestBed.
The available authority endpoints are documented in this OpenAPI specification under the For Authorities section.