Download Interactive HTML Export

Step 11: Download the interactive HTML export

The real product export โ€” a single self-contained HTML file rendered server-side by the same job that produces the audit-trail PDF, carrying the same ten sections plus a live verdict-coloured plot map. This is what to hand a customer, a regulator or your own front end; the previous step is only a quick Bruno-side preview built from the JSON report.

Prerequisite

This workflow created the record but never asked for an export, so run Generate Audit Trail Export first:

POST /regulations/eudr/audit-trail/{{ddsdf_record_id}}/audit-trail   {}

Poll that task to completed, then run this step (which polls again for the HTML itself โ€” see Timing below).

What this step does

GET /regulations/eudr/audit-trail/{{ddsdf_record_id}}/audit-trail/html returns a JSON envelope carrying short-lived signed URLs, not the bytes. An HTML export is always exactly one file:

FieldMeaning
files[0].download_urlSigned GCS URL โ€” GET it to download the file. No API key needed
expires_atWhen the link(s) stop working
files[0].size_bytesSize of the export (a few MB for a small record; tens of MB for thousands of plots)
stale / rebuildingWhether the stored file still reflects the current audit trail

The after-response script follows the link and renders the result in the Visualize tab, so you see the actual export rather than a reconstruction.

Timing: this step polls

The HTML is written last, after the PDF and the package, as an additive step that can never fail the render job. So there is a window where the generate task already reports completed and the HTML does not exist yet. The endpoint reports that as 425 Too Early, and this step retries on it (20 attempts, 3s apart) before asserting.

A 404 is different: it means no export exists for this version at all, so generate one first. A 425 that never clears means the HTML render itself failed โ€” it cannot fail the task, so the PDF and package are still valid; re-run the render with ?force=true to retry it.

Hosting it

The signed link pins Content-Disposition: attachment, so it always downloads and never renders in place. For a durable, shareable page: fetch the bytes once, store them, and serve them from a URL you control. ?ttl= accepts up to 604800 (7 days) if you need a wide window for the transfer.

See Download Audit Trail HTML for the full contract.

Required scope: eudr:read