Version boundary
Pin API/schema/profile versions in test evidence.
DEVELOPER GUIDEREFERENCE CONTRACT
Claims API
Create, query, supersede and dispute evidence-backed claims with issuer/source/version context.
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 |
POST
/v1/claimsSubmit an evidence-backed claim
Submit an evidence-backed claim for governed evaluation and lifecycle management.
- OAuth
- claim.write
- State
- Evidence and issuer context exist; claim is not yet accepted. → Claim enters governed processing; acceptance is not equivalent to legal authority.
- Evidence
- Evidence references, issuer context, policy version and audit record.
- Errors
- 400 schema · 401/403 scope/mandate · 409 duplicate/idempotency · 422 policy/evidence failure
- Retry
- Use Idempotency-Key for write retry.
{"subject":"ttid:thing:01HV...","claimType":"ownership","issuer":"org:example","evidenceRefs":["evidence:transfer:123"]}{"claimId":"claim:01...","status":"pending-governed-evaluation","correlationId":"corr-..."}GET
/v1/claims/{claimId}Get a claim and provenance/status context
Read a claim together with provenance and status context.
- OAuth
- claim.read
- State
- Claim identifier is known. → Current governed claim/status context is returned.
- Evidence
- Read audit according to policy; provenance links preserved.
- Errors
- 404 claim not found · 403 disclosure denied
- Retry
- Safe read retry.
{"subject":"ttid:thing:01HV...","claimType":"ownership","issuer":"org:example","evidenceRefs":["evidence:transfer:123"]}{"claimId":"claim:01...","status":"pending-governed-evaluation","correlationId":"corr-..."}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.