Download Audit Trail GeoJSON
Get download links for the TRACES-ready geolocation file โ the GeoJSON you upload to the EU Information System yourself when you file your own DDS, instead of having us file it for you.
It is built by the same job as the PDF: call Generate Audit Trail Export once and the PDF, the package, the HTML and this file are all produced together. This endpoint hands you links to the finished files; it doesn't build them.
โถThis is not the package's geometry file
There are two geometry documents in this API and they are not interchangeable:
| This endpoint | The export package's geojson/ | |
|---|---|---|
| Scope | Included, compliant plots only | Every plot on the version |
| Purpose | What you file to TRACES | Evidence for a competent authority |
| Matches a submit | Yes โ the same plot set we would file, when there is one to file (see below) | No |
Uploading the package's file to the portal would declare plots you did not intend to declare. Use this one to file.
The plot set is what matches a submit, not the bytes. When we file for
you over SOAP, each feature is re-wrapped and its properties are stripped, so
that payload is a different encoding of the same plots and has a different
size. The limit applies per part, so measure each part against it with that
part's own wire_bytes.
โถWhy there can be more than one file
A record with many plots produces a document too large to handle as one file, so the export is split into parts, each sized to fit the 25 MB base64 measure ยง14 applies.
files carries every part, ordered by part. Fetch all of them โ a
partial set is not the complete plot set.
How to file a multi-part export is NOT yet settled
Do not assume you can upload several parts against one DDS. Our reading of ยง14 "Geolocation data size" is 25 MB per DDS, not per uploaded file โ which is why our own submit path splits an over-large record across multiple TRACES filings rather than across multiple files on one filing. On that reading a record whose parts total more than 25 MB cannot be filed as one DDS however it is divided.
So: a single-part export is unambiguous โ file it. If your export has more than one part, check the current TRACES specification, or let us file it for you, before you upload. Getting this wrong risks a non-compliant declaration.
EPO-2717 tracks confirming the rule against the acceptance environment.
โถResponse
| Field | Description |
|---|---|
file_count | Number of parts this export is made of |
total_size_bytes | Sum of size_bytes across files |
expires_at | When the links stop working โ the earliest expiry across the parts |
files[].part | 1-based ordinal within the artefact |
files[].filename | Name the signed URL serves the file under, carrying its part number |
files[].download_url | A direct, short-lived link โ GET it to download. No API key needed |
files[].content_type | Always application/geo+json |
files[].size_bytes | Size of the part |
dds_hash | The report this export was rendered from. Artefacts of one record with the same value come from the same report state; while stale it names the stored report, not the current one |
stale | true when the audit trail changed since these parts were written |
rebuilding | true when a fresh render is currently in progress |
manifest | Per-part accounting โ see below |
โถThe manifest
Assembled from the stored parts, so it always describes the files
files points at.
| Field | Description |
|---|---|
include | Always compliant โ the filing scope, stated so it cannot be confused with the package's file |
dds_hash | The report fingerprint these parts were built from |
part_count | Number of parts |
feature_count | Total plots across every part |
total_wire_bytes | Sum of the parts' base64 lengths โ what the portal measures |
max_wire_bytes_per_part | The per-part ceiling currently in force. Parts written by an earlier render may have been split against a different one |
parts[].part | 1-based ordinal, joining this entry to files[].part |
parts[].feature_count | Plots in that part |
parts[].raw_bytes | Stored size of that part as recorded at write time; normally equal to files[].size_bytes |
parts[].wire_bytes | The base64 length of that part โ this, not size_bytes, is what the 25 MB limit applies to |
parts[].oversized | true when one single plot already breached a writer bound on its own โ the base64 ceiling above, or a larger raw-size bound not reported here, so an oversized part can still show wire_bytes under max_wire_bytes_per_part. Splitting cannot help; the geometry itself has to be reduced |
โถAn empty export means there is nothing to file
A record with no compliant included plots still returns 200, with one
part holding an empty FeatureCollection and manifest.feature_count: 0.
That is deliberate โ a 404 here would read as "never generated" and send a
correct client away.
Do not file it. A submit for that version is refused (422 PRE_SUBMISSION_BLOCKED), because TRACES rejects a declaration with no
geolocation. Check manifest.feature_count before you upload: 0 means the
record needs plots included or verdicts resolved first, not that the export
failed.
โถOutdated exports rebuild automatically
Like the PDF, these parts are tied to the exact state of the audit trail. Excluding or including a plot, editing a justification or overriding a verdict makes them stale.
This endpoint still returns 200 with the current (now-outdated) parts, but
flags stale: true and starts a fresh render (rebuilding: true). Poll until
both are false, then fetch the new links.
Do not file a stale export. Its scope may no longer match the plots you are declaring.
โถAvailability after a render
| Code | When |
|---|---|
200 | The parts are ready โ download links returned |
425 Too Early | The render is running, or the parts have not landed yet. Retry |
404 | No export exists for this version โ generate one first, or the record/version isn't visible to this caller |
404 | The version was filed before this export existed and its render is frozen, so it can never be produced. Its message says so; every other 404 here shares the generic wording |
401 | No API key, or an unrecognised one |
403 | The key lacks the eudr:read scope |
503 | Temporarily unable to produce links โ try again shortly |
A generic 404 can also mean the stored artefact is internally inconsistent โ
its rows exist but their objects do not. Re-run the render; if it persists,
contact support.
A version rendered before this export existed has a PDF and no parts. That is treated as stale and rebuilt automatically, so it converges on its own.
The one case that does not converge is a version already filed before this
export existed: its render is frozen, so no rebuild can run. It answers 404
saying so. Use the export package's geolocation file as the record of what was
filed.
โถLink lifetime
By default the links are valid for 3600 seconds (1 hour). Pass
?ttl=<seconds> for a different lifetime, up to 604800 โ 7 days. Respect
expires_at rather than computing your own deadline: it is the earliest
expiry across the parts, so a caller that honours it is never caught out by
one part lapsing before the rest.
โถA specific version
GET /regulations/eudr/audit-trail/:recordId/versions/:versionId/audit-trail/geojson
returns links for a specific historical version's export. Same behaviour.
Required scope:
eudr:read