EUDR Information System - Operator API Reference¶

Welcome to the EUDR SOAP API documentation for operators, micro or small primary operators, and authorised representatives integrating with the EUDR Information System.

Overview¶

The EU Deforestation Regulation (EUDR), Regulation (EU) 2023/1115, requires operators placing relevant commodities (cattle, cocoa, coffee, oil palm, rubber, soya and wood) on the EU market to demonstrate that their products are deforestation-free and produced in compliance with the legislation of the country of production.

The regulation establishes an Information System where operators submit due diligence statements before market placement or export.

Concerning the amendment procedure of the Implementing Regulation (EU) 2024/3084 that is currently undergoing, this version of documentation may not be final and will be adapted as needed. In particular, certain features such as the grouping of submissions and versioning of Simplified Declarations are planned for subsequent releases and may not be available in the first release. Readers are encouraged to check the European Commission website for updates and subscribe to the Newsletter for the latest information.

Quick Start¶

Base URL¶

Environment	Base URL
Production	`https://eudr.webcloud.ec.europa.eu/tracesnt/`
Acceptance	`https://acceptance.eudr.webcloud.ec.europa.eu/tracesnt/`

Which service do I use?¶

You are...	Service	Endpoint
An operator or authorised representative placing products on the market or exporting	DDS — Due Diligence Statement	`/ws/EUDRDueDiligenceStatementServiceV3?wsdl`
A micro or small primary operator established in a low-risk country, producing and placing own products	SD — Simplified Declaration	`/ws/EUDRSimplifiedDeclarationServiceV3?wsdl`
Testing connectivity and WS-Security credentials	Echo — Connectivity Test	`/ws/EudrEchoService?wsdl`

Authentication¶

Both services use WS-Security (UsernameToken over HTTPS):

Transport: HTTPS with TLS
Token: UsernameToken with PasswordDigest (hashed)
Timestamp: Required (wsu:Created / wsu:Expires)
Header: WebServiceClientId - your client identifier, visible in the "Web Services Access" section of your profile (see Acquiring Credentials)

Multi-Operator Support (BodyIdentity Header)¶

If your API user account is linked to more than one operator, you must include a BodyIdentity SOAP header to specify which operator you are acting as for each request. The header contains the operator's Web Service Access Identifier — a unique code assigned to each operator by the system administrator.

<soapenv:Header>
    <!-- WS-Security and WebServiceClientId as usual -->
    ...
    <body:BodyIdentity xmlns:body="http://ec.europa.eu/tracesnt/body/v3">
        <OperatorAccessIdentifier>YOUR_IDENTIFIER</OperatorAccessIdentifier>
    </body:BodyIdentity>
</soapenv:Header>

Scenario	Behaviour
User linked to one operator, no `BodyIdentity` header	Works as before — operator resolved automatically
User linked to one operator, `BodyIdentity` header present	Header is used to resolve the operator
User linked to multiple operators, `BodyIdentity` header present	Header resolves the specific operator
User linked to multiple operators, no `BodyIdentity` header	Request rejected — the system cannot determine which operator to use

Finding your Operator Access Identifier

The Web Service Access Identifier is visible in the EUDR Information System under Directory → Operators → [your operator] → Operator Identifiers section. Contact your system administrator if the identifier has not yet been assigned.

Supported identifier types

Only OperatorAccessIdentifier is accepted for EUDR endpoints. Other identifier types (AuthorityActivityAccessIdentifier, OrganicControlBodyAccessIdentifier, OtherBodyAccessIdentifier) defined in the schema are not supported and will be rejected.

Child element namespace

The OperatorAccessIdentifier child element must be in no namespace (unqualified). Do not apply the parent's namespace prefix to it. See the XML example above for the correct format.

XSD access¶

Replace ?wsdl with ?xsd=1, ?xsd=2 etc to retrieve the XSD schema (refer to the <xs:import> section in the WSDL for schema numbering).

Service availability

The V3 endpoints and WSDLs listed above are not yet accessible and will become available once the system goes online. As noted above, the service contracts are subject to change as the amendment of the Implementing Regulation (EU) 2024/3084 is finalised.

Target audience¶

This documentation is intended for:

Economic operators with IT systems that manage DDS electronically and wish to automate submission to the EUDR Information System
Authorised representatives acting on behalf of operators
Micro or small primary operators submitting simplified declarations
Software providers developing solutions to service operators' needs in submitting DDS or SD to the EUDR system

Contact information¶

Purpose	Contact
Registration and technical support	SANTE-TRACES@ec.europa.eu
Policy questions (Deforestation Regulation)	ENV-DEFORESTATION@ec.europa.eu
Implementation guidance	Deforestation Regulation implementation

Note

When contacting technical support, email titles must start with "EUDR API". Questions should concern API behaviour, testing, errors, or integration.

Versioning policy¶

Service versions are identified by the suffix in the endpoint URL (e.g., V3).

When a new version is released without backward compatibility, the previous version remains available for a transition period to allow operators to adapt their systems.
For the production environment, the duration of version coexistence is published in advance.
Old versions are decommissioned after the transition period — operators are required to switch to the latest available version.
Readers are invited to regularly verify whether new specifications are published, as services and their behaviour may evolve.

API version history¶

The EUDR Information System API has been released in three major versions:

V1 - the initial API, released with the original Regulation (EU) 2023/1115. Supported DDS submission and retrieval for operators.
V2 - an incremental update to V1 with additional retrieval operations and minor data model refinements. Both V1 and V2 supported only the Due Diligence Statement (DDS).
V3 (current) - a redesign driven by Regulation (EU) 2025/2650, which introduced new actor types (micro or small primary operators, downstream operators), the Simplified Declaration (SD), and grouped declarations. V3 replaces the V1/V2 service contracts with new namespaces, operations, and data structures.

The Migration Guide and Field-Level Mapping sections document the detailed differences between versions.

Previous API versions (V1 and V2)¶

API versions V1 and V2, which were available before the entry into application of Regulation (EU) 2025/2650, will be decommissioned with the release of V3. The regulatory amendment introduces structural changes to the data model and service contracts that are not backward-compatible.

Due diligence statements submitted before the amendment remain accessible in read-only mode through the V3 API.