> 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/additional-resources/achieving-eudr-compliance.md).

# Achieving EUDR compliance

The EUDR compliance workflow can be separated into different steps:

1. An importer of the seven different commodities and derived products needs to resolve the supply chain down to the individual plot level
   1. The importer needs to identify its tier 1 suppliers
   2. The suppliers need to provide any plots of land or tier >1 suppliers
2. The importer needs to assess the deforestation status of all the plots
   1. Using historical and current satellite imagery
   2. Using custom questionnaire answers by suppliers
   3. Using supplier-provided documents
3. Once the plots in the supply chain are approved, they can be used in due diligence statements submitted automatically to the EU Information System

Below is a documentation of how to achieve each of these steps through the TradeAware Application Programming Interface (API).

*Note: These endpoints and fields are in various degrees of implementation and subject to future change.*

### Provide plots via App, API or bulk upload <a href="#supplier-provide-plots-via-app-api-bulk-upload-or-dds-reference" id="supplier-provide-plots-via-app-api-bulk-upload-or-dds-reference"></a>

Operators and suppliers on the platform can provide plots that are under their administration. This can be done manually by drawing the plot boundaries onto the provided map, by bulk uploading plots through a file upload dialog or by using again the API:

`curl -X POST https://api.tradeaware.live-eo.com/plots -H ... -d '{"commodities": ["soy"], ..., "geometry": {"type": "Polygon", { "coordinates": [[[...],[...],[...],[...]}}'`

This can also be done in bulk per commodity or list of commodities:

`curl -X POST https://api.tradeaware.live-eo.com/plots/batch -H ... -d '{"commodities": ["soy"], ..., "geometries": [{"type": "Polygon", { "coordinates": [[[...],[...],[...],[...]}}, ...]'`

While the API and the bulk upload method support both geojson polygons and multipolygons, the application only supports polygons for now.

### Get plots and suppliers risk-assessed via App and API <a href="#get-plots-and-suppliers-risk-assessed-via-app-and-api" id="get-plots-and-suppliers-risk-assessed-via-app-and-api"></a>

The next step following the collection of suppliers and plots is the assessment of the deforestation state of the plots. You can request an open source data analysis on a plot using the following `POST` endpoint:

`curl -X POST https://api.tradeaware.live-eo.com/plots/{plotId}/analyses -H ... -d '{"type": "EUFOROBS"}`

and checking for the `status` field (`['PENDING', 'RUNNING', 'SUCCEEDED', 'FAILED']`) in the response body, which will indicate whether the analysis results are already available. An alternate approach of using webhooks is part our future roadmap.


---

# 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/additional-resources/achieving-eudr-compliance.md?ask=<question>&goal=<user_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.