Skip to main content

v0.99.6: Integration API for ERP and PLM systems and BMS data freshness

Introduces the headless Integration API, giving ERP and PLM systems a machine-readable path for authoring Digital Product Passports. Also adds a BMS data freshness label to battery passports.

Integration API​

ERP, PLM and manufacturing execution systems can now author Digital Product Passports over HTTP without using the operator portal.

The Integration API covers the pre-publication lifecycle:

  • Create a DPP draft from product data in your source system
  • Update fields incrementally as data becomes available
  • Attach evidence documents such as test reports and certifications
  • Check the publish gate to see which required data is still missing
  • Submit the completed draft to the Traceable review queue

A person in your team reviews and publishes the passport in the portal, so the published record carries their attribution. Each customer uses its own API key, writes are protected by idempotency keys and requests are signed. Five scopes are available at this release: dpp:read, dpp:draft:write, dpp:gate:read, dpp:submit and document:write.

Availability: the Integration API is generally available. See Integration API: build and manage passports from your own systems and the Integration API documentation.

Access requests for restricted fields​

Fields reserved for market surveillance authorities, customs bodies and other persons with a legitimate interest are available through the access-request flow, and authorised requests see the full set of fields that apply to them. Fields that are not restricted are unchanged for anyone with the QR code or link.

BMS freshness label​

Battery passports for products connected to a Battery Management System now show when the BMS data was last received, so readers can tell whether the performance and health figures are current. The label appears on the public passport and in the JSON-LD output.