Batch registration file for the EU DPP Registry.
Builds the batch file an economic operator uploads to the EU DPP Registry, as XML. Sibling of the JSON-LD and EPCIS tenant exports.
Publishing a passport does not register it. The duty to register sits with the economic operator placing the product on the market (Reg (EU) 2023/1542), and TracePass has no registry client. This endpoint hands over the payload already in the shape the registry accepts, so the step the operator owes is an upload rather than a data-assembly exercise.
Batteries only — BATTERIES is the only product group the registry offers, so passports in other categories are excluded rather than exported into a group the registry would reject. The response reports how many were left out, so the caller is not guessing.
Published passports only: an unpublished passport's link does not resolve, and the registry probes it mechanically.
At most 100 items per file.
Not API-key reachable. Auth is dashboard JWT with the admin role — the same privileged-action gate as the other tenant exports. There is deliberately no plan gate: this is the customer's own regulatory obligation, and putting a paywall between them and a duty they cannot otherwise discharge is not a trade worth making.
Synchronous response with Content-Disposition: attachment.
Request
- Base URL: https://app.tracepass.eu
- URL: https://app.tracepass.eu/api/exports/tenant/registry-batch
- Auth: API key in cookie tp_session
Response
The batch registration file.
Changes
No recorded changes to this operation across all 1 revision of this API.