TracePass
Reference

Restricted passport data

How a partner or authority reads restricted passport fields with an access grant (a pa_ token): ?access= or Bearer, role filtering for batteries, caching.

A published passport shows its public fields to everyone. Other fields are restricted to the parties that need them: a repairer, a recycler, a buyer, a market surveillance authority. The operator gives such a party an access grant, a pa_ token, and the party presents it when it reads the passport. This page covers what the holder sends and what comes back.

Read a passport with a grant

Send the grant to the passport's own address, the one the QR code resolves to, in either of two ways: as Authorization: Bearer pa_… or as the query parameter ?access=pa_…. The Bearer header suits programs; the query parameter suits a link, but a URL ends up in browser history and server logs, so prefer the header where you can. The grant works on the passport page, its JSON-LD, PDF, EPCIS and data views.

bash
curl -H "Authorization: Bearer pa_REDACTED_xxxxxxxxxxxx" \
  -H "Accept: application/ld+json" \
  https://id.tracepass.eu/01/99999999999997/21/6B27A0000001

The same request with the query parameter:

text
https://id.tracepass.eu/01/99999999999997/21/6B27A0000001?access=pa_REDACTED_xxxxxxxxxxxx

A pa_ token is for reading a published passport. It does not authenticate calls to /api/v1, which take a tp_ API key or OAuth. A grant that is unknown, expired, revoked, or does not cover this passport is not refused: the request gets the public view, as if no grant had been sent.

What the grant lets you see

The operator issues each grant to a named role: repairer, remanufacturer, repurposer, recycler, waste treatment, training centre, buyer or buyer's agent, end-of-life vehicle or WEEE treatment, market surveillance, notified body, Commission, customs or other. It is scoped to the whole company, to chosen products or to chosen passports. Authority roles see their whole tier.

For batteries, the role decides which Annex XIII data the holder sees: a repairer sees the spare-part and dismantling data, a buyer the data of the battery it bought, and so on. The mapping follows the Commission's draft implementing act under Battery Regulation Article 77(9). That act is not adopted and the draft can change, so treat the mapping as provisional.

A field the role does not cover is not left out silently. The passport viewer shows it as "not part of this access grant" (in the viewer's language), so the holder can tell a field hidden by the grant from a field the passport does not carry. Data outside the fields, such as lineage, service history and EPCIS events, follows the same rule.

Lifetime and the read log

A grant expires after 12 months by default. A buyer's grant has no expiry and ends when a change of owner is recorded for the battery. The operator can revoke any grant at any time. When the grant is issued, the purpose and the evidence the operator checked are recorded with it. That evidence is recorded, not verified: TracePass does not check the holder's identity.

Every read that serves content through a grant is logged, counted per grant, passport, channel (page, JSON-LD, PDF, EPCIS, data) and day. The log holds no IP address.

Caching

A response to a grant is Cache-Control: private, no-store with Vary: Authorization. Do not cache it in a shared cache or pass it on: it contains data the public view does not.