EUDR Guide
  1. Home
  2. EUDR Information System
  3. EUDR API

EUDR Information System

EUDR API: The SOAP Web Services for Submitting Due Diligence Statements and Simplified Declarations

EUDR API explained: the SOAP web services for due diligence statements and simplified declarations, credentials, acceptance tests and the one-hour wait.

Last updated 19 November 2026 · By the EUDR Guide Editorial Team · How we fact-check · Print this page

The EUDR API is the set of SOAP web services through which the Commission lets operators file due diligence statements and simplified declarations system-to-system in the EUDR Information System (Article 9(e) of Implementing Regulation (EU) 2024/3084).

Filing duties come from the EU Deforestation Regulation, Regulation (EU) 2023/1115: a statement is filed before the product is placed on the market or exported, and kept for five years (Article 4(2) and (3)).

The rules below cover the services, version, credentials, environments, limits and payload.

  • Protocol: SOAP with WS-Security UsernameToken; no official REST API.
  • Version: V4 is current as of 14 November 2026; V3 is in transition.
  • Rate limit: 10,000 calls per minute globally.
  • Wait: at least one hour after submission before retrieving the reference number.

What Is the EUDR API?

The EUDR API is a "machine-to-machine connection" to the EUDR Information System that manages statements in bulk, as an alternative to the web interface (Commission Green Forum page on the information system).

Legal Basis: Article 9(e) of Implementing Regulation 2024/3084

Article 9(e) of Implementing Regulation (EU) 2024/3084 makes the Commission provide web services for users "to submit and manage Due Diligence Statements and Simplified Declarations, including grouping thereof ... in an automated manner".

Article 15(4)(a) lets the Commission set "technical limits for file size" and regulate "the frequency of interactions". Article 18(1) puts the costs of the system on the Commission, so the API is free of charge.

SOAP, Not REST: Why Some Offers Say Otherwise

The Commission publishes no official REST API: the services use SOAP over HTTPS (Operator API documentation, as of 14 November 2026). REST interfaces on the market are third-party wrappers around the SOAP services.

Which Services and Operations Does the EUDR API Offer?

The EUDR API offers three services, for due diligence statements, simplified declarations and an echo test, used by the roles OPERATOR and REPRESENTATIVE_OPERATOR (Operator API documentation; an authorised representative may submit for the operator under Article 6 of Regulation (EU) 2023/1115).

Service Endpoint name (V4) Operations Who uses it
Due diligence statement EUDRDueDiligenceStatementServiceV4 submitDds, amendDds, withdrawDds, getDds, getDdsByInternalReference (getDdsByIdentifiers returns no detail) Operators and authorised representatives
Simplified declaration EUDRSimplifiedDeclarationServiceV4 submitSd, updateSd, withdrawSd, getSd, getSdByInternalReference (getSdByIdentifiers returns no detail) Micro or small primary operators in low-risk countries
Echo EudrEchoService testEcho Anyone testing credentials, acceptance only

The DDS Service: Submit, Amend, Withdraw and Retrieve

The DDS service submits a statement with submitDds, which returns a UUID, and manages it with amendDds (the reference number stays the same) and withdrawDds. The overview calls return the status, reference number and verification number. In V4, getDdsByIdentifiers returns no statement detail (NotFoundException), so detail is read only in the web interface (change log).

The Simplified Declaration Service: Submit, Update and Withdraw

The simplified declaration service files the one-time declaration of Article 4a with submitSd, changes it with updateSd after major changes and cancels it with withdrawSd. The simplified declaration is for micro or small primary operators, and who may file one is set out there.

The producer location is sent as GeoJSON, as a postal address (street, postal code and city) or as a cadastral identifier of up to 80 characters.

The Echo Service: Testing Credentials in Acceptance

The testEcho operation confirms that credentials work and exists in the acceptance environment only (Echo service page). The request timestamp must lie within five minutes of server time.

Which EUDR API Version Is Current? V4, V3 and the Transition

As of 14 November 2026, V4 is current for the operator services; V3 remains available during a transition without a published end date.

Version What it added Status as of 14 November 2026
V1 DDS submission and retrieval Decommissioned with V3
V2 Extra retrieval operations, DDS only Decommissioned with V3
V3 Redesign for Regulation (EU) 2025/2650: simplified declarations and grouping Available during the transition, to be deprecated
V4 Evolution of V3 for the operator services; no detail retrieval by identifiers; EudrUserMessage response header; referenceNumberInfo status Current, target for new integrations
Competent Authority service Service for authorities Stays at V3

V4 adds the optional referenceNumberInfo status ("Under system analysis", "Under Competent Authority review (Article 17)", "Assigned") to overview responses and an EudrUserMessage header of up to 2,000 characters (change log).

How Do You Get API Credentials After Registering an Operator?

API credentials belong to an EU Login user of a registered operator. Operators first register in the EUDR Information System; one account per user can hold several roles (Article 10(1) and (2) of Implementing Regulation (EU) 2024/3084).

  1. Take the EU Login username of the user.
  2. Create the private Authentication Key under Edit Profile, Web Services Access.
  3. Test in acceptance first, then use the credentials in production.
  4. Name a real responsible person: the EU Login user answers for the data submitted.

Authentication: WS-Security UsernameToken and Timestamp

The services authenticate with a WS-Security UsernameToken carrying a PasswordDigest, over HTTPS, with a timestamp and a WebServiceClientId (Operator API documentation).

One API User, Several Operators: The Web Service Access Identifier

A user who serves several operators needs one Web Service Access Identifier per operator, sent as OperatorAccessIdentifier in the BodyIdentity header (Multi-Operator Support section of the documentation). Four behaviours follow.

  • New operators receive the identifier automatically.
  • Existing operators request it from SANTE-TRACES@ec.europa.eu.
  • Each call names the operator it is made for.
  • Several linked operators without the header: the request is rejected.

Only submissions in the production environment have legal value; the acceptance environment is a test replica (Green Forum page on the information system). Registrations are separate in each environment.

Production runs at https://eudr.webcloud.ec.europa.eu/tracesnt/ and acceptance at https://acceptance.eudr.webcloud.ec.europa.eu/tracesnt/.

Limits and Timing: Rate Limits, the One-Hour Wait and the 72-Hour Window

The API allows 10,000 calls per minute globally and 5 calls per second per IP address, adjustable with system load; sustained abuse may lead to suspension of the account (Acquiring Credentials page). Article 15(4)(a) of Implementing Regulation (EU) 2024/3084 allows such limits.

Limit Value Source
Calls, globally 10,000 per minute Acquiring Credentials page
Calls per IP address 5 per second Acquiring Credentials page
Retrieval by UUID 100 per call Acquiring Credentials page
Retrieval by internal reference 1,000 per call Acquiring Credentials page
Wait before reference number or status At least one hour Acquiring Credentials page
Amend or withdraw 72 hours after the reference number is made available IR 2024/3084, Art. 5(1)
Geolocation per statement 25 MB Validation Rules
Commodities per statement 200 Validation Rules
Producers 1,000 per commodity, 10,000 per statement Validation Rules
Referenced statements 2,000 Validation Rules
Clock tolerance Five minutes Echo service page

Why Wait One Hour Before Retrieving the Reference Number?

Wait at least one hour after submitting before retrieving the reference number or checking the status, because numbers are assigned only after risk profiling (as of 14 November 2026; the documentation said 30 minutes in October). Under Article 7(1) and (2) of Implementing Regulation (EU) 2024/3084 the reference number and verification number are assigned without undue delay and made available when risk profiling concludes. Format and sharing are covered under EUDR reference number.

Amending or Withdrawing Through the API Within 72 Hours

A statement can be amended or withdrawn within 72 hours after its reference number was made available (Article 5(1) of Implementing Regulation (EU) 2024/3084).

Amendment is blocked once the statement is used in a grouping, a check is notified, the goods are placed or exported or the number is given to customs (Article 5(2) and (3)); the extension is at most 8 calendar days (Article 5(4)).

The API documentation starts the window when the entry becomes AVAILABLE; the regulation governs. After expiry amendDds returns EUDR_API_AMEND_DEADLINE_ELAPSED, and a new statement is submitted.

What Goes Into the Payload: GeoJSON Geolocation, Grouping and File Size

The payload carries geolocation as base64-encoded GeoJSON with at least six decimal digits, and polygons for plots of more than four hectares other than cattle (Article 2(28) of Regulation (EU) 2023/1115). The duty itself is explained under EUDR geolocation.

Statements can be grouped under Article 8a of Implementing Regulation (EU) 2024/3084, inserted by Implementing Regulation (EU) 2026/1565; the User Guide allows up to 1,000 members per group head, and the geolocation of one statement is limited to 25 MB (Validation Rules).

Element Rule Source
geometryGeojson Base64 GeoJSON geometry, at least six decimal digits Art. 2(28)
Polygons Plots of more than 4 ha, not cattle Art. 2(28)
Simplified declaration location GeoJSON, postal address (street, postal code, city) or cadastral identifier up to 80 characters SD V4 page
groupedDeclarations Grouping under Art. 8a; up to 1,000 members (User Guide); not allowed on amend IR 2024/3084; User Guide; DDS V4 page
File rules Tested in the EUDR GeoJSON Checker Validation Rules

Every rule on this page is checked against Implementing Regulation (EU) 2024/3084 and the Commission's Operator API documentation; see how EUDR Guide verifies every fact. Placement on EUDR Guide is never sold.

This guide explains the rules; it is not legal advice for an individual case.

How Does the API Connect to the Information System, Statements and Software?

The API connects to the same system as the web interface, set up under Article 33 of Regulation (EU) 2023/1115. It is one door into the EUDR Information System.

What a due diligence statement must contain is set by Annex II, whichever door is used.

Software Integrations: Who Is Responsible for What Is Submitted?

Responsibility for what is submitted stays with the operator, because software vendors are not users of the system (Article 3(c) of Implementing Regulation (EU) 2024/3084). Credentials belong to an EU Login user of the operator. What platforms do is covered under EUDR software.

EUDR API FAQ

The seven answers below cover the questions developers ask most. More answers are in the EUDR FAQ.

Is an API Connection Mandatory?

No: statements and declarations can be filed in the web interface, and only the free EUDR Information System itself is required. The operator stays responsible for every submission (Articles 4(3) and 6(1) of Regulation (EU) 2023/1115).

Does the EUDR API Cost Anything?

No: the Commission bears the costs of setting up, maintaining and operating the system (Implementing Regulation (EU) 2024/3084, Article 18(1)). The web interface and the web services are both free for users.

Can Downstream Operators or Traders Use the API?

A downstream operator or trader files no due diligence statements since 26 December 2025 (Article 5 of Regulation (EU) 2023/1115), so the filing services are built for operators and authorised representatives. Who counts as a downstream operator or trader follows from Article 2.

Where Is the Official API Documentation Published?

On the Commission's EUDR portal, as the Operator API Reference with WSDL files, samples, migration guides and a change log, and in a CIRCABC folder that developers should check regularly.

What Happens If the System Is Unavailable?

For unplanned unavailability exceeding 60 minutes, Article 15a of Implementing Regulation (EU) 2024/3084 requires contingency measures, including contingency reference numbers, and a public website by 30 December 2026.

Will the Authentication Method Change?

Yes, in a later release: mutual TLS authentication is planned without a published date, and the UsernameToken method stays during a transition period (change log, as of 14 November 2026).

Where Do Developers Get Technical Support?

Write to SANTE-TRACES@ec.europa.eu with a subject starting "EUDR API" on API behaviour, testing, errors or integration. Name the operation, the environment and the error returned, so the question can be answered.

Sources