DEVELOPER GUIDEREFERENCE CONTRACT

Quick Start

Integrate a reference resolver and DPP read flow, then add policy, evidence and connector behavior as scope requires.

Integration GuideDeveloper CenterAPI Center
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.

FIRST FLOW

Resolve → read → decide → evidence.

Start with read-only synthetic data, then add protected actions after purpose/mandate and evidence requirements are explicit.

GET /v1/resolve/{identifier}
Authorization: Bearer <token>
X-Correlation-ID: 9b2...

200 {
  "officialIdentifier": "...",
  "resolvedThingId": "ttid:...",
  "authority": {"type":"external-domain"},
  "assurance": {"level":"context-dependent"}
}
Event
+
Authorized actor
+
Precondition
+
Evidence
+
Trusted time
+
Policy / profile version
=
Resulting state
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.

Request a workshopExplore architecture