Test and Conformity Assessment Data Integration

Move test-report and certification data from a testing laboratory or conformity assessment body into a Digital Product Passport. AI extraction from a PDF certificate, REST API for teams that want to push data programmatically, and signed outbound webhooks that notify downstream systems on verification events.

Start Free Book a Demo

Test data is mandatory, and it usually arrives as a PDF

The EU Battery Regulation requires that a battery passport carry durability and performance test values, safety test results (UN 38.3, IEC 62619, IEC 62660), conformity assessment references, and the identity of the issuing body. A conformity assessment body issues a certificate as a PDF. A test lab returns a report as a PDF. The compliance team then re-keys the numbers into a passport field by field. That is the exact workflow this page addresses.

Traceable is the receiving infrastructure for that data. Not a replacement for the lab or the certification body, and not a claim to any partnership with a specific named body.

Three paths for moving test and certification data into a DPP

Path 1

Upload the certificate PDF and let AI extract the fields

Upload the certificate you received. AI auto-detects the document type (UN 38.3 transport, IEC 62619 stationary safety, CE Declaration of Conformity, REACH SVHC declaration, carbon-footprint verification, due-diligence report, technical data sheet) and extracts the regulatory fields the passport needs: certificate number, issuing body, standards referenced, sample identity, issue date, expiry, and pass or fail status. Every extracted value comes with a per-field confidence score. Nothing is bound to the passport until a human reviewer accepts it.

Path 2

Programmatic push through the REST API

Labs and conformity assessment bodies that want to push data programmatically can use Traceable's REST API v1. The operator whose passport is being updated issues an API key with the scope they choose; the lab uses that key to attach documents and update the compliance fields on the products they are testing. Signed requests, per-tenant scoping, and a full audit trail of every write.

Path 3

Signed outbound webhooks keep downstream systems in sync

When a document is verified, a passport is published, a compliance gate changes state, or a submission is received, Traceable can fire a signed HMAC webhook to a URL of your choice. Suitable for LIMS, QMS, or ERP systems that need to react in real time to a passport-side event, or for laboratories that want to close the loop when a customer accepts their upload.

Document types the AI extractor recognises

The extractor has a schema for each of the certificate shapes below. Upload the PDF and the shape is auto-detected. Extraction runs against the schema, so extracted output maps cleanly to the corresponding passport fields.

UN_38_3                : Lithium battery transport test summary
IEC_62619              : Stationary and industrial cell safety
CE_DECLARATION         : CE Declaration of Conformity
REACH_DECLARATION      : REACH SVHC declaration and SCIP references
CARBON_FOOTPRINT       : Carbon-footprint verification statement
DUE_DILIGENCE          : Supply-chain due-diligence report
TECHNICAL_DATA_SHEET   : Product-level technical data sheet

Extracted values arrive with per-field confidence scores. Everything is queued for human review; nothing auto-commits to the passport.

How a lab or certification body pushes data programmatically

When the operator being tested wants their lab to push data directly into the passport, the operator issues a per-tenant API key with a defined scope. The lab uses that key to attach documents and update compliance fields on the operator's products. There is no separate lab portal or lab-only endpoint; the entry point is the same REST API v1 that any programmatic caller uses, with permissions bounded by the key.

POST  /api/v1/documents                Upload a certificate PDF against a product
PATCH /api/v1/products/{id}            Update compliance fields on a product
GET   /api/v1/products/{id}            Confirm the update landed as expected
POST  /api/v1/webhook-endpoints        Subscribe to document_verified events

See the full API reference and endpoint list →

Verification events available on the outbound webhook

Traceable emits signed HMAC webhooks that a downstream system can consume to stay in sync with what is happening on the passport side.

  • document_verified - fires when a verifier accepts an uploaded certificate
  • dpp_published - fires when a passport is published to the public URL
  • gate_changed - fires when a compliance gate changes state
  • dpp_withdrawn - fires when a passport is withdrawn from public view
  • submission_received - fires when a supplier or lab submits data for review

What Traceable does not do

Being clear about the boundary matters more here than on any other integration page, because the market includes major named certification bodies and it would be easy to imply a partnership that does not exist.

  • Traceable does not ship a native TUV, Bureau Veritas, SGS, or Intertek API connector. Where the workflow uses those bodies today, it is a PDF certificate that a human uploads into Traceable, or an API push from an operator-authorised key.
  • There is no dedicated inbound lab portal or lab-only endpoint. The path is the same REST API v1 that any programmatic caller uses.
  • Traceable does not issue verified credentials on behalf of a certification body. What we store is the certificate document, the extracted fields, the reviewer identity, and the timestamped audit entry.
  • There is no automated round-trip between a lab, Traceable, and the passport back to the lab. Each direction is a discrete step.

Partnerships with testing labs and certification bodies

Active pilots are welcomed with laboratories and conformity assessment bodies. A partnership today means a small joint engagement with a shared customer: the lab tests the sample, Traceable holds the passport, and we work out the data path between the two. No productised connector with a named body exists yet, and we will not claim one until it ships.

Start a partnership conversation

Get test and certification data into the passport.

Start Free Book a Demo

Further reading

Platform

AI Document Intelligence

Auto-detection and schema-bound extraction for UN 38.3, IEC 62619, CE, REACH, and other certificate types.

Platform

API Reference (dev.traceable.digital)

The REST API v1 endpoints a laboratory or conformity assessment body would call to push test data with an operator-issued key.

Industry

Battery Passport Compliance

How the extracted test and certification data lands in the durability, performance, and conformity fields of the passport.

Related: LCA and Carbon Platform Integration  ·  Partners overview