There is no single EU government API. EU government API integration in 2026 means connecting to a set of separate systems that share one design: an EU-level standard or central platform, plus national entry points where you actually plug in. This map shows which systems that covers, who must connect to each, and the date each one starts to matter.
Last reviewed: 23 October 2026. Every status below is as of that date.
What changed in 2026:
- The Entry/Exit System became fully operational across the Schengen area on 10 April 2026. Carriers have had to query eu-LISA’s carrier interface since that date; voluntary use began on 9 January 2026.
- Regulation (EU) 2024/1028 began to apply on 20 May 2026, so short-term rental platforms now report to national single digital entry points.
- Member States must offer at least one EUDI Wallet by 24 December 2026, about two months away.
- ETIAS still has no start date. The Commission’s ETIAS page dropped its last-quarter-of-2026 target in July 2026.
Is there one EU government API?

No. The EU publishes standards and runs a few central platforms, but the endpoints you connect to are almost always operated by Member States. The same pattern, an EU standard plus a national gateway, shows up in the four systems integrators ask about most:
- The Once-Only Technical System (OOTS) is defined by Implementing Regulation (EU) 2022/1463 under Article 14 of Regulation (EU) 2018/1724. The legal deadline for Member States was 12 December 2023, when 21 procedures listed in Annex II had to be available fully online. Public authorities connect through eDelivery Access Points; businesses do not call OOTS directly.
- BRIS, the Business Registers Interconnection System under Directive 2012/17/EU, runs through a European Central Platform that, according to the Commission, orchestrates all traffic among national business registers and the European e-Justice Portal. Registers connect to it; companies deal with their own national register.
- The EUDI Wallet comes from Regulation (EU) 2024/1183. Each Member State issues its own wallet, and a business that wants to request data from wallets registers nationally and identifies itself with an access certificate.
- Under Regulation (EU) 2024/1028, each Member State that runs a registration scheme for short-term rentals builds its own single digital entry point (SDEP). There is no EU-level SDEP: Article 18 tells the Commission to evaluate by 20 May 2031 whether a central one is needed.
Which EU government systems have APIs? Most do, but none is a front door for the whole EU. That is why government EU API integration is a per-system, per-country task. The one real exception is the carrier interface for the Entry/Exit System, covered in the map below.
EU government API integration map: the systems an integrator actually meets
If you came looking for an EU government APIs list, this table is the closest accurate version. It lists systems and their entry points rather than APIs, because no EU-wide API catalogue exists to list. It also shows how to integrate with EU government systems at a practical level: first find out whether the endpoint is central or national, then who must connect. OOTS, BRIS and EUDI Wallet integration each put a different party on the hook.
| System | Who must connect | EU or national endpoint | Key date |
|---|---|---|---|
| OOTS (once-only technical system) | Competent authorities as evidence requesters or evidence providers, directly or through intermediary platforms. Businesses trigger exchanges from a procedure portal. | EU common services (Data Service Directory, Evidence Broker, Semantic Repository) plus a national eDelivery Access Point | 12 December 2023 |
| Interoperable Europe Act assessments | Union entities and Member State public bodies setting binding requirements for trans-European digital public services. Not companies. | National competent authority and single point of contact; Interoperable Europe Board at EU level | 12 January 2025 (Act applies from 12 July 2024) |
| EES and ETIAS carrier interface (Regulation 2017/2226, Regulation 2018/1240) | Carriers checking third-country nationals before boarding: air, sea and international coach operators | One EU endpoint run by eu-LISA: REST over mutual TLS, MQ over VPN, web portal or mobile app | 10 April 2026 for EES queries (voluntary from 9 January 2026); ETIAS: no date announced |
| Short-term rental SDEPs (Regulation 2024/1028) | Online short-term rental platforms; hotels and campsites are out of scope | One national SDEP per Member State with an API built on Commission technical requirements; no EU endpoint | 20 May 2026 |
| EUDI Wallet (Regulation 2024/1183) | Member States issue wallets; businesses and public bodies that request wallet data register nationally; regulated private parties must accept wallets from 24 December 2027 | National wallet and national relying-party register under Implementing Regulation 2025/848; EU-level rules and implementing acts | 24 December 2026 |
| BRIS and company-law digitisation (Directive 2025/25) | National business registers; companies file with their own register | European Central Platform and e-Justice Portal at EU level; each national register | Transposition by 31 July 2027; 15 working days for companies to file changes |
| ViDA digital reporting (Directive 2025/516, Regulation 2025/517) | VAT-registered businesses making intra-EU B2B supplies, or providers reporting for them | National tax-authority systems that feed the Commission’s central VIES | 1 July 2030 |
How to read the map
Only the carrier interface is a single EU endpoint, because eu-LISA, the EU agency that runs the Entry/Exit System, operates the central system behind it. According to eu-LISA’s carrier interface overview, one query covers up to 99 passengers and each passenger gets an OK or NOK answer. When ETIAS starts, the same interface will return ETIAS authorisation results too.
Everything else hands data to national systems, so integration effort scales with the number of countries, not the number of EU systems. A rental platform reports monthly and machine-to-machine to each Member State’s SDEP (Article 9(1)); small and micro platforms under 4,250 listings may report quarterly and manually (Article 9(2)). Austria runs its SDEP through the federal ministry responsible for tourism and gives platforms a dedicated mailbox for connecting. The Portuguese law firm MCS Advogados points out that SDEP data adds a registration-and-activity stream to two that already exist, CESOP on the payment leg and DAC7 on the platform leg, and expects the three to be cross-referenced increasingly.
These EU national access points for government data are where credentials, test environments and support desks actually live. A legal date is also not an adoption date. The Commission’s own February 2026 explainer says OOTS has been operational since 2023 and describes national authorities as only now beginning to use it. For the EUDI Wallet, B2Trust sorted the 27 Member States into three readiness tiers as of April 2026, eight months before the deadline.
National exchange layers: X-Road as the reference model
X-Road, which Estonia calls X-tee, is the reference design for a national exchange layer. Each member installs its own security server, and traffic between members is encrypted and signed. Estonia’s Information System Authority (RIA) says the data owner keeps control throughout and the technology only provides the secure exchange. In its case study of the Estonian system, Privacy International describes every message as timestamped and logged by the security server, while a central server holds only the registry of members and the security policy.
Estonia and Finland have developed the software together since a 2013 memorandum, and since 2018 the Nordic Institute for Interoperability Solutions (NIIS) has been its main developer. The two countries run a trust federation that lets members in one environment use services in the other. The OOTS Hub lists X-Road among its reusable services, with REST and SOAP among its technologies. To use an existing X-tee service you become a member, install a security server and agree terms with the service provider, according to RIA. The security-server certificates are requested through RIA’s self-service environment.
What the 2020 API framework got right and what is still missing
The Joint Research Centre’s API framework for digital government (2020) offers 12 proposals arranged in four pillars: policy support, platforms and ecosystems, people, and processes. The proposals include harmonising platform and ecosystem assets, setting up cross-competency teams, appointing API product managers and adopting an API lifecycle approach. Its diagnosis was right: government APIs are as much an organisational problem as a technical one.
The obstacles that ADVANT Beiten lawyers Dennis Hillemann and Johannes Voß-Lünemann listed for German public administration in May 2025 show the same pillars failing in practice:
- Fragmentation: the federal structure produced different systems and standards at federal, state and municipal level.
- Legacy systems without modern APIs, which need middleware or costly modernisation.
- Data protection rules that can restrict the exchange of personal data between authorities, so GDPR compliance has to be designed into the API architecture.
- Weak governance and standardisation, because common API standards are hard to enforce across autonomous authorities.
- Resource and skills gaps, above all in municipalities, made worse by the IT skills shortage in the public sector.
Fragmentation and legacy sit in the platforms pillar, governance in policy support, and skills in people. What the 2020 framework could not contain is the legal layer that came after it. OOTS went live in 2023. The Interoperable Europe Act made interoperability assessments mandatory from 12 January 2025 for decisions that introduce or change binding requirements for trans-European digital public services. Regulation 2024/1028 lets the Commission set common technical specifications for SDEPs (Article 10(5)). The EU’s answer to the API problem has been mandates and per-system specifications, not a shared API catalogue, which is why a map like this one is the useful artefact for an integrator.
Sector duties that turn into API work
Hotels and similar accommodation are excluded from Regulation 2024/1028 (Article 3(1)), so a hotel’s reporting duties come from national law, and each country has its own interface. Three duties recur: guest registration with the police, accommodation statistics for the national statistics office, and tax clearance or e-invoicing reporting. The rental regulation adds one statistical flow of its own: Article 12(4) requires monthly transmission of activity data to national statistical offices and to Eurostat. The rest of this section is what I have run into on the integrator side. Names of countries, regulators and employers are removed on purpose; the patterns hold across jurisdictions.
Police guest registration: certificates and delegation
The police guest-register web service I have integrated against is SOAP over HTTPS, and every submission is signed with a certificate. Two things cost me time. The certificate that ships with the documentation is valid for the test environment only, so a working test integration says nothing about production access. And the registration form asked for identifiers that only the regulated establishment holds, an establishment code and a tourism registration number, which a software provider does not have. The police replied that each establishment must authorise the provider’s tax ID so that the provider signs submissions with its own certificate. An establishment may not hand its own certificate to a third party.
If you submit on behalf of hotels, ask the regulator early which delegation model it supports. In this case a shared credential was ruled out.
Accommodation statistics: record the test credentials
For a national statistics office’s upload portal, I found that test-environment credentials had been issued to the integrator earlier and nobody could locate them. Recovering them meant writing to the office. The practical rule is to log test identifiers on the day they are issued, and to ask for the technical documentation in the same request.
Tax clearance: a published requirement is not a published procedure
In one tax-reporting regime I examined, the requirements for becoming a certified transmission provider are published, but the certification procedure is not, and I could not reach anyone who runs it. Before committing a roadmap to a country, ask who runs provider certification, what it takes and how long it takes. Asking before the build is cheaper than finding out after it.
Where SOAP survives
SOAP is still current in several places that matter to integrators. VIES, the VAT number validation service, publishes a SOAP WSDL and a REST interface side by side. OOTS messages travel over eDelivery AS4, and Denmark’s Agency for Digital Government describes the AS4 headers as part of a SOAP/ebMS3 header in its OOTS connection guide. X-Road supports both SOAP and REST. In my own work SOAP survives in national regulator services and inside EU messaging standards such as AS4. The newest central system in this map, the carrier interface, uses REST over mutual TLS or MQ over VPN instead.
Timeline to 2030
- 12 December 2023: legal deadline for OOTS. Representatives of 25 Member States took part in the Commission’s go-live event on 11 and 12 December 2023.
- 12 January 2025: interoperability assessments become mandatory under the Interoperable Europe Act, which applies from 12 July 2024.
- 9 January 2026: the carrier interface opens for voluntary use. 10 April 2026: carrier queries become mandatory and the Entry/Exit System is fully operational.
- 20 May 2026: Regulation 2024/1028 applies, and Member States must have adopted penalty rules for platforms by the same date (Article 15(4)).
- 24 December 2026: each Member State must offer at least one EUDI Wallet, 24 months after the first implementing acts entered into force on 24 December 2024, as Garrigues sets out.
- Date not announced: ETIAS. As of 23 October 2026 the Commission’s ETIAS page says only that the system is not in operation and that the start date will be announced several months before launch. SchengenVisaInfo reported on 19 October 2026 that the last-quarter-of-2026 wording disappeared from the official site in July. Pages that still repeat the Q4 2026 target are out of date.
- 31 July 2027: transposition deadline for Directive (EU) 2025/25, which sets a 15-working-day window for companies to file changes to their registered information, as Forvis Mazars’ Belgian summary of the Directive notes.
- 24 December 2027: private relying parties covered by Article 5f(2) of Regulation 910/2014, as amended, must accept the EUDI Wallet when a user asks them to.
- 1 July 2030: ViDA digital reporting for intra-EU B2B supplies. Member States feed the transaction data into a central VIES that the Commission builds under Regulation 2025/517, as the European Parliament’s summary of that Regulation explains.
One date falls just beyond the horizon: by 20 May 2031 the Commission must evaluate the rental regulation, including whether a central SDEP at Union level is needed.
Frequently asked questions
Can a company call OOTS directly?
No. OOTS is a government-to-government data space: evidence requesters and evidence providers, which are competent authorities, connect to its common services, directly or through intermediary platforms. A business or citizen triggers an exchange by explicitly requesting it in an online procedure portal, after seeing a preview of the evidence, according to the Once-Only Hub. If you build a procedure portal or an intermediary platform for a public body, you do connect, through an eDelivery Access Point.
Does an integration need a qualified certificate?
There is no single rule. Each system sets its own trust model, and none of the sources I checked for this map names a qualified certificate as the entry requirement. OOTS Access Points use X.509 certificates that a Member State can bring itself or request from the eDelivery PKI, which issues up to two per Member State for its Access Points, according to the OOTS service desk. The carrier interface’s REST option runs over mutual TLS. An EUDI relying party identifies itself to wallets with an access certificate from a certificate authority its Member State has authorised under Implementing Regulation 2025/848. The police service I integrated against signs submissions with the integrator’s own certificate. Read each onboarding pack before you buy a certificate.
Which EU systems still use SOAP?
VIES offers a SOAP service alongside REST, OOTS eDelivery messages carry SOAP/ebMS3 headers, and X-Road supports SOAP and REST. National regulator services are the other big group; the police guest-register service described above is one. The carrier interface for the Entry/Exit System offers REST or MQ rather than SOAP.
Who certifies intermediaries?
No single EU body does. For OOTS, Implementing Regulation 2022/1463 makes Member States responsible for installing and integrating eDelivery Access Points in procedure portals, data services and intermediary platforms, and the Commission’s playbook for national coordinators strongly encourages conformance-tested Access Points. The closest thing to EU-run certification I found is eu-LISA’s onboarding path for carriers and their service providers: registration, a security convention, a pre-compliance phase against a simulator, a compliance phase in the test environment with pre-defined test cases, sign-off, then go-live, as laid out in its implementation process.
