TracePass
Reference

DPP scope check

Check whether a product needs a DPP — from when and the duties of each role. Single check on every plan; catalogue check from Growth.

POST/api/v1/scope/check

Check DPP scope

Returns a structured regulatory answer for a product type: whether it needs a Digital Product Passport, from when, at which level (item or model), the governing act and article, the duties of the requesting party's role, which other acts also apply, and any open questions that must be answered before a definitive verdict can be given. Every answer names the article it rests on, or says when our rules do not cover the product.

GET/api/v1/scope/catalogue

Get catalogue scope report

Returns the catalogue scope report: for every product (and every distinct passport fact set), whether the product type needs a Digital Product Passport, from when, at which level, the governing act and article, and the passport status (`missing`, `draft_only`, `published_incomplete`, `published`, `not_required`, `open_questions`, or `not_covered`). The full answer for any item is `POST /api/v1/scope/check` with its `productId`.

POST/api/v1/scope/catalogue/runs

Start a catalogue run

Triggers a fresh catalogue scope run that re-checks the whole catalogue against the current rules. The run queues immediately and executes asynchronously; the response is 202 with a `runId` to poll. The catalogue also refreshes nightly automatically.

GET/api/v1/scope/catalogue/runs/{id}

Get catalogue run status

Returns the status and evaluation counts for one catalogue scope run. Poll this endpoint after `POST /api/v1/scope/catalogue/runs` until `status` is `done` or `failed`. Once done, the fresh results are available via `GET /api/v1/scope/catalogue`. A run belonging to another company returns 404.

POST/api/v1/scope/reports

Report a wrong answer

Submits a correction report to a review queue. Use `ruleIds` from the `ruleIds` field of the scope-check or regulatory-assistant response envelope to route the report to the right rule owner quickly. The `what` field is a plain-language description of what is wrong or unclear — be specific: include the product type, the facts you used, and what the answer said that was wrong.