202 Accepted with a jobId. Use the Jobs API to track progress, then retrieve the finalized payload once processing completes.
Endpoint
POST /api/v1/enterprise/eudr/declarations/dds
Request Parameters
The unique identifier of the verified and risk-assessed batch for which you are generating the DDS. The batch must have a
COMPLIANT status before this call will succeed.An array of SHA-256 hashes representing the land tenure and legality documents associated with this batch. Each hash should correspond to a document previously uploaded via the Upload Legal Land Tenure Document endpoint. These hashes are anchored to the Hedera ledger as cryptographic proof of land rights at the time of DDS generation.
Response Fields
The unique identifier of the asynchronous DDS generation job. Use this ID to monitor progress via the Jobs API. Once the job reaches
COMPLETED status, call GET /api/v1/enterprise/eudr/declarations/dds/{referenceId} to retrieve the finalized XML payload.The initial status of the job. Always
PENDING immediately after acceptance.An advisory estimate of how many seconds the generation job is expected to take before completing.
ISO 8601 timestamp indicating when the DDS generation job was accepted and enqueued.
Code Examples
Example Response
DDS generation is asynchronous. After receiving a
202 Accepted, poll GET /api/v1/enterprise/eudr/jobs/{jobId} to track the job phase. Once it reaches COMPLETED, retrieve the finalized XML payload using GET /api/v1/enterprise/eudr/declarations/dds/{referenceId}. The referenceId is returned in the job’s result metadata.The batch referenced by
batchId must have completed satellite deforestation screening and hold a COMPLIANT risk status before a DDS can be generated. Attempting to generate a DDS for a PENDING or HIGH_RISK batch will return a 422 Unprocessable Entity error.