Enterprise integration guidance for Trusted ThingID resolver, DPP, claims, evidence, lifecycle, connectors, events, sandbox and conformance.
A connector or client is not release-ready until the exact interface version, environment, limits and acceptance evidence are known.
Reference contracts are intentionally explicit about boundaries and failure semantics.
Integrate a reference resolver and DPP read flow, then add policy, evidence and connector behavior as scope requires.
Use OAuth/OIDC patterns where applicable, scoped tokens, purpose and mandate context; never conflate AuthN, AuthZ and field disclosure.
Reference REST contracts for resolver, DPP, claims, evidence, mandate, lifecycle, search, device trust and connector operations.
Resolve official identifiers and aliases while returning source/authority context and assurance metadata.
Read and manage policy-qualified DPP resources without making the API itself the authority for every field.
Create, query, supersede and dispute evidence-backed claims with issuer/source/version context.
Record evidence references, provenance, trusted time, integrity and retention metadata.
Represent delegation and mandate lifecycle independently from identity and ownership.
Apply attributable, policy-versioned material transitions with preconditions and evidence.
Search derived read models without treating search indexes as authoritative records.
Versioned authority context, delivery semantics, retry, reconciliation, degraded mode and exit controls.
Asynchronous lifecycle, claim, evidence and connector events with correlation and replay-safe semantics.
Signed or authenticated callback patterns with idempotency and delivery evidence.
Canonical JSON schema baseline for claims, evidence, lifecycle events and connector status.
Runnable-oriented examples and integration patterns; source package ships reference contracts rather than claiming production SDK certification.
Project sandbox model with synthetic data, environment separation and no production secrets.
Test exact profile/version/environment combinations and retain evidence for release approval.
Use these as design baselines and version them for each real deployment.
REST operations, business semantics and examples
Events, delivery, verification and retry
Schema purpose, versioning and validation
Use the collection after understanding identity, mandate and lifecycle
Credentials · API explorer · webhooks · sandbox · conformance
Applications Clients List
API Catalogue Catalogue
Sandbox Work List
Conformance Evidence Assessment Result
Decision-grade products, maturity and boundaries.
Operating scope, roles, failures and version.
Version-aware profiles and test evidence.
Positive/negative tests and expected evidence.
What is actually ready, external or deployment-specific.
Align product-group applicability, authority boundaries, portal journeys, integration contracts and evidence before committing to production claims.
