DEVELOPER GUIDEREFERENCE CONTRACT

DPP API

Read and manage policy-qualified DPP resources without making the API itself the authority for every field.

CONTRACT PRINCIPLES

The protocol carries business semantics.

Each integration must preserve authority, policy, evidence and recovery context.

Version boundary

Pin API/schema/profile versions in test evidence.

Correlation

Carry a correlation ID across request, event, connector and evidence records.

Idempotency

Protect material write operations from accidental replay.

Authority context

Never infer legal authority solely from transport success.

REFERENCE ENDPOINTS

Explore the full OpenAPI contract.

The downloadable contract contains request/response models, OAuth scopes, idempotency and representative errors.

Reference API surface
AreaReference routeSemantics
ResolverGET /v1/resolve/{identifier}Official ID → TTID resolution with authority context
DPPGET /v1/dpp/{identifier}Policy-qualified DPP read
ClaimsPOST /v1/claimsEvidence-backed claim submission
EvidencePOST /v1/evidenceEvidence/provenance reference
MandatePOST /v1/mandatesDelegation lifecycle
LifecyclePOST /v1/things/{thingId}/transitionsMaterial transition
SearchGET /v1/searchDerived read model
ConnectorPOST /v1/connectors/{id}/reconcileBusiness reconciliation
VIEW ONLINE FIRSTYAML is a download artifact; operation semantics are read here.
GET/v1/dpp/{identifier}

Read a policy-qualified DPP view

Read a policy-qualified DPP view for the resolved product context.

OAuth
dpp.read
State
Identity, purpose, mandate and disclosure context are evaluated. → A composed public/restricted view is returned; source records remain authoritative.
Evidence
Policy/disclosure decision may be audited according to deployment policy.
Errors
404 no view · 401/403 denied · 424 authoritative source unavailable where applicable
Retry
Safe read retry; degraded-mode behavior must be explicit.
{"identifier":"0950600012345","purpose":"consumer-view"}
{"identifier":"0950600012345","view":"public","profileVersion":"example-2026.1","fields":{"model":"Example Product"},"authority":{"registryStatus":"external-source"}}
ARCHITECTURE WORKSHOP

Move from integration to evidence-backed approval.

Align product-group applicability, authority boundaries, portal journeys, integration contracts and evidence before committing to production claims.