Version boundary
Pin API/schema/profile versions in test evidence.
DEVELOPER GUIDEREFERENCE CONTRACT
Connector Contracts
Versioned authority context, delivery semantics, retry, reconciliation, degraded mode and exit controls.
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/connectors/{connectorId}/healthGet connector operational state
Read operational connector state without conflating transport health with authoritative business status.
- OAuth
- connector.read
- State
- Connector exists. → Operational health is returned.
- Evidence
- Operational telemetry and connector-status evidence.
- Errors
- 404 connector · 403 operations scope
- Retry
- Safe read retry.
{"connectorId":"eu-dpp-registry"}{"connectorId":"eu-dpp-registry","transport":"healthy","businessReconciliation":"required","authority":"external"}POST
/v1/connectors/{connectorId}/reconcileRequest business/system reconciliation
Request business/system reconciliation after retry, outage or ambiguous external outcome.
- OAuth
- connector.operate
- State
- A discrepancy or ambiguous external outcome has been identified. → Reconciliation workflow is queued; external authority remains external.
- Evidence
- Trigger reason, source/target state, retry history and reconciliation result.
- Errors
- 409 reconciliation already active · 422 unsupported discrepancy · 503 external system unavailable
- Retry
- Idempotent request; reconciliation is distinct from transport retry.
{"connectorId":"eu-dpp-registry"}{"connectorId":"eu-dpp-registry","transport":"healthy","businessReconciliation":"required","authority":"external"}CONNECTOR PROFILES
Authority, failure and reconciliation are part of the contract.
CONN-REGEXTERNAL DEPENDENCY
DPP Registry Connector
- External party
- EU/external DPP Registry
- Authoritative domain
- Registry status
- Protocol/Profile
- External spec/profile
- Authentication
- Project credentials
- Authorization
- Organisation/authority context
- Events
- dpp.registry.*
- Failure / Retry
- Timeout/retry with idempotency
- Reconciliation
- Business reconciliation mandatory on ambiguity
- Evidence
- Request/response digest + source status
CONN-IAMREFERENCE IMPLEMENTATION
Enterprise IAM / OIDC
- External party
- Identity Provider
- Authoritative domain
- Identity/authentication
- Protocol/Profile
- OIDC/OAuth profile
- Authentication
- OIDC
- Authorization
- Scopes/roles/mandates
- Events
- identity.*
- Failure / Retry
- Fail closed / step-up
- Reconciliation
- Re-authenticate / mandate resolution
- Evidence
- Auth/decision audit
CONN-ERPPILOT READY
ERP / PLM Connector
- External party
- Enterprise source systems
- Authoritative domain
- Product master / EO source
- Protocol/Profile
- REST/project mapping
- Authentication
- Deployment-selected
- Authorization
- Service account/role
- Events
- product.source.*
- Failure / Retry
- Retry safe reads; controlled writes
- Reconciliation
- Source reconciliation
- Evidence
- Source digest + mapping evidence
CONN-TSAREFERENCE ARCHITECTURE
TSA / Evidence Renewal
- External party
- Trusted time/archive service
- Authoritative domain
- Trusted time / LTV evidence
- Protocol/Profile
- RFC 3161 / selected ETSI profile
- Authentication
- Service credential
- Authorization
- Evidence service role
- Events
- evidence.time.*
- Failure / Retry
- Retry; preserve original evidence
- Reconciliation
- Renew/reverify by policy
- Evidence
- Timestamp/renewal evidence
CONN-DEVPKIREFERENCE ARCHITECTURE
Device PKI / Attestation
- External party
- Device CA / Verifier
- Authoritative domain
- Certificate / runtime evidence
- Protocol/Profile
- PKI + selected attestation
- Authentication
- Device/service credentials
- Authorization
- Device operations policy
- Events
- device.*
- Failure / Retry
- No blind retry on failed appraisal
- Reconciliation
- Re-attest / rotate / quarantine / restore
- Evidence
- Cert lifecycle + appraisal evidence
CONN-MKTREFERENCE IMPLEMENTATION
Marketplace Connector
- External party
- Marketplace / dealer systems
- Authoritative domain
- Listing / sale context
- Protocol/Profile
- Connector contract v1
- Authentication
- Project credential
- Authorization
- Marketplace role
- Events
- marketplace.*
- Failure / Retry
- Retry/idempotency by operation
- Reconciliation
- Reconcile listing vs authoritative status
- Evidence
- Verification/listing evidence
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.