Three channels, as Jesse described them
Regulation (EU) 2023/1543 has applied since August 18, 2026. On August 6, twelve days before that, Jesse Goodman, VP Product Delivery at Kodex, told the Kodex EU e-Evidence Prep Talk how orders would reach a service provider. He said there were “three different approaches” surfacing, which he expected to change over time.
- An API. Built to the ETSI standard.
- Alternative channels. Kodex, email, fax and other systems already in use.
- A reference system with no API. A member state with its own system and no interest in the alternatives.
The API to the ETSI standard
Kodex has built an API to the ETSI standard, which Jesse suggested everybody read if they haven’t. He said the standard is detailed about the technical architecture and how to set it up. He called the API “the ideal solution down the road when it is available.”
“We have built an API to the ETSI standard, which I suggest everybody take a look at if you haven’t already.”
Jesse Goodman, VP Product Delivery, Kodex
In August Jesse was seeing delays “across pretty much every member state” in opening the API for testing and implementation, so Kodex was also pursuing other paths.
Alternative channels, Kodex among them
Jesse said Kodex, email, fax and the regular portals that exist today still apply when a member state has no reference infrastructure, or no systems in place to serve requests and receive responses. These alternative means, through Kodex or other channels, remain available for the day-one deadline, he said, especially if the bills pass in the member states that are in scope for a provider.
The third pattern is a member state with a reference system in place and no API, and potentially no wish to use the alternative channels. Jesse expected all three approaches to evolve.
Where to read more
The Kodex guide to EU e-Evidence covers who is in scope and the deadlines, and a European Production Order is defined in the glossary. The Prep Talk replay has the whole session.
For the deadline once an order arrives, see How long do you have to answer an EU e-Evidence order? For what a team needs ready, see What do you need in place to handle EU e-Evidence orders?
In Jesse’s words
We have built an API to the ETSI standard, which I suggest everybody take a look at if you haven’t already. It is very detailed about the technical architecture and how to set it up. I think it is the ideal solution down the road when it is available, though we’re seeing delays across pretty much every member state in opening it up for testing and implementation.
We are also pursuing alternative paths. Kodex, email, fax and the regular portals that exist today still apply for member states that may be in scope for requests to you as a service provider, but that do not have reference infrastructure or their systems in place to serve requests and receive responses. These alternative means, through Kodex or through other channels, are still available for the day-one deadline, especially if the bills for the legislation are passed within the member states that are in scope for you. That’s definitely one method.
We are also seeing a third channel, where there might be a reference system in place for a member state but no API, and potentially no desire to use alternative channels. So there are three different approaches that are definitely surfacing, and I think they will evolve over time.
Edited for length and clarity. From the EU e-Evidence Prep Talk, August 6, 2026