Version boundary
Pin API/schema/profile versions in test evidence.
DEVELOPER GUIDEREFERENCE CONTRACT
Resolver API
Resolve official identifiers and aliases while returning source/authority context and assurance metadata.
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 |
GET
/v1/resolve/{identifier}Resolve an official identifier or governed alias
Resolve an official identifier or governed alias while returning authority and assurance context.
- OAuth
- thing.read
- State
- Identifier is presented; no platform authority is inferred. → A resolution result and source-authority context are returned; no legal relationship changes.
- Evidence
- Resolution/correlation audit context; no material business state change.
- Errors
- 404 unknown identifier · 401/403 authentication/authorization · 409 ambiguous/collision context where implementation requires review
- Retry
- Safe read retry with correlation ID.
{"identifier":"0950600012345"}{"officialIdentifier":"0950600012345","resolvedThingId":"ttid:thing:01HV...","aliases":["urn:epc:id:sgtin:..."],"authority":{"domain":"official-identifier","source":"issuing-scheme"},"assurance":{"level":"source-aware"}}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.