Version boundary
Pin API/schema/profile versions in test evidence.
DEVELOPER GUIDEREFERENCE CONTRACT
API Reference
Reference REST contracts for resolver, DPP, claims, evidence, mandate, lifecycle, search, device trust and connector operations.
CONTRACT PRINCIPLES
The protocol carries business semantics.
Each integration must preserve authority, policy, evidence and recovery context.
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.
| 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 |
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.