> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/tradeaware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/tradeaware/using-the-tradeaware-api/api-reference/transactions/retrieve-dds-data.md). # Retrieve DDS Data Fetch a Due Diligence Statement from the EUDR TRACES system by its reference and verification numbers. `GET /dds/fetch-dds-data` fetches a Due Diligence Statement (DDS) from the EU's EUDR TRACES system using its reference number and verification number. Use it to check that a DDS exists, and to see what it contains, before you attach it to a transaction component. You can also call it on its own. TradeAware sends the request to the TRACES environment configured for your business. More info about the EUDR TRACES system: [EUDR information system](https://green-business.ec.europa.eu/deforestation-regulation-implementation/information-system-deforestation-regulation_en). ## Fetch Due Diligence Statement data from EUDR Traces system > More info about EUDR Traces system: ```json {"openapi":"3.0.0","info":{"title":"TradeAware API","version":"0.57.0"},"servers":[{"url":"https://api.tradeaware.live-eo.com"}],"security":[{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"scheme":"bearer","bearerFormat":"JWT","type":"http"}}},"paths":{"/dds/fetch-dds-data":{"get":{"description":"More info about EUDR Traces system: https://green-business.ec.europa.eu/deforestation-regulation-implementation/information-system-deforestation-regulation_en","operationId":"DdsController_fetchDdsData","parameters":[{"name":"verificationNumber","required":true,"in":"query","description":"The verification number of the DDS","schema":{"type":"string"}},{"name":"referenceNumber","required":true,"in":"query","description":"The reference number of the DDS","schema":{"type":"string"}}],"responses":{"200":{"description":"The DDS data. When TRACES_API_V3_ENABLED is on, `statement.status.status` can be any value from the full EudrStatusType set (SUBMITTED, AVAILABLE, REJECTED, WITHDRAWN, ARCHIVED, SUSPENDED, UPDATED, GROUPED, OBSOLETE) — a superset of the V1-era DdsStatusType, and without V1's CANCELLED value, which has no V3 equivalent."},"400":{"description":"Incorrect reference or/and verification number"},"403":{"description":"The business does not have permission to manage transactions"},"429":{"description":"Too many requests - Limit: 2 requests per 10 seconds"},"503":{"description":"The DDS data could not be fetched from EUDR Traces system"}},"summary":"Fetch Due Diligence Statement data from EUDR Traces system","tags":["DDS"]}}}} ``` ## Requirements * **Authentication:** a bearer token (JWT) in the `Authorization` header. * **Entitlement:** your business's plan must include managing transactions. * **Rate limit:** 2 requests every 10 seconds. ## Example response
200 OK ```json { "statement": { "activityType": "IMPORT", "representedOperator": { "operatorAddress": { "country": "DE", "street": "CONFIDENTIAL", "postalCode": "CONFIDENTIAL", "city": "CONFIDENTIAL" }, "operatorName": "one nam" }, "commodities": [ { "position": 1, "descriptors": { "descriptionOfGoods": "Coffee, whether or not roasted or decaffeinated; coffee husks and skins; coffee substitutes containing coffee in any proportion", "goodsMeasure": { "netWeight": "12.000000" } }, "hsHeading": "0901", "producers": [ { "country": "ID", "geometryGeojson": "" }, { "country": "EE", "geometryGeojson": "" } ] } ], "geoLocationConfidential": false, "status": { "status": null, "date": null } } } ```
## Response notes * Each entry in `producers` has a `geometryGeojson` field. It holds a **base64-encoded** GeoJSON `FeatureCollection`, so decode it before use. * Operator address fields can come back as `CONFIDENTIAL` when the operator has withheld them. * `geoLocationConfidential` shows whether the DDS owner has marked the geolocation as confidential. {% hint style="info" %} When TradeAware reads from the TRACES API v3, `status.status` and `status.date` are returned as `null`. This is a temporary placeholder: on v3 there is currently no way to look up verification status from a reference and verification number. These fields will hold a real status once TRACES' Verification service is integrated. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.live-eo.com/tradeaware/using-the-tradeaware-api/api-reference/transactions/retrieve-dds-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.