Version boundary
Pin API/schema/profile versions in test evidence.
Read and manage policy-qualified DPP resources without making the API itself the authority for every field.
Each integration must preserve authority, policy, evidence and recovery context.
Pin API/schema/profile versions in test evidence.
Carry a correlation ID across request, event, connector and evidence records.
Protect material write operations from accidental replay.
Never infer legal authority solely from transport success.
The downloadable contract contains request/response models, OAuth scopes, idempotency and representative errors.
| Area | Reference route | Semantics |
|---|---|---|
| Resolver | GET /v1/resolve/{identifier} | Official ID → TTID resolution with authority context |
| DPP | GET /v1/dpp/{identifier} | Policy-qualified DPP read |
| Claims | POST /v1/claims | Evidence-backed claim submission |
| Evidence | POST /v1/evidence | Evidence/provenance reference |
| Mandate | POST /v1/mandates | Delegation lifecycle |
| Lifecycle | POST /v1/things/{thingId}/transitions | Material transition |
| Search | GET /v1/search | Derived read model |
| Connector | POST /v1/connectors/{id}/reconcile | Business reconciliation |
/v1/dpp/{identifier}Read a policy-qualified DPP view for the resolved product context.
{"identifier":"0950600012345","purpose":"consumer-view"}{"identifier":"0950600012345","view":"public","profileVersion":"example-2026.1","fields":{"model":"Example Product"},"authority":{"registryStatus":"external-source"}}Align product-group applicability, authority boundaries, portal journeys, integration contracts and evidence before committing to production claims.