Home/Integration & Developer/Delivery and acceptance

Trusted Records · Integration & Developer

Delivery and acceptance

Record accepted sets/decisions against manifests; billing is separately reconciled.

Service Playground — task-based experience OpenAPI and Swagger Reference

Request schema from OpenAPI

Field	Type	Required	Constraints	Technical definition
`manifestVersion`	integer	Yes	`{"minimum": 1}`	Expected version of the delivery manifest; refresh after a conflict.
`acceptedRefs`	array	Yes	`{"minItems": 1}`	Subset of records in the delivered manifest; no out-of-manifest acceptance.
`decision`	string	Yes	`{"enum": ["PARTIAL_ACCEPTANCE", "ACCEPTED", "CORRECTION"], "minLength": 1}`	Authorized acceptance, partial acceptance or correction decision.

Read the operation and next actions

Swagger · deliver

Errors and next actions

A consistent error envelope guides recovery without disclosing sensitive data.

Read details

Reliability, concurrency and recovery

Retry design follows the side effect rather than repeating every request blindly.

Read details

API Explorer — local simulator

Explore requests/responses and failure scenarios using synthetic data; no backend connection.

Read details

Input, scopes and processing

POST /v1/deliveries/{deliveryId}/acceptance · scope delivery:accept. Tenant/project and correlation contexts are required. POST/PATCH use Idempotency-Key; examples/schemas below are proposed contracts.

States and outputs

DELIVERED → REVIEW → PARTIAL_ACCEPTANCE / ACCEPTED / CORRECTION. No automatic invoice.

Exceptions and controls

Manifest version mismatches return 409; out-of-manifest sets or permissions return 422/403.

HTTP example — proposed contract

Request

POST https://records.example.invalid/v1/deliveries/{deliveryId}/acceptance HTTP/1.1
Authorization: Bearer <example-token>
X-Tenant-Id: synthetic-tenant-001
X-Project-Id: synthetic-project-001
X-Correlation-Id: synthetic-correlation-001
Idempotency-Key: synthetic-key-001
Content-Type: application/json

{
  "manifestVersion": 1,
  "acceptedRefs": [
    "synthetic-record-001"
  ],
  "decision": "PARTIAL_ACCEPTANCE"
}

Response · 202

{
  "acceptanceRef": "synthetic-acceptance-001",
  "status": "RECONCILING",
  "billableEvaluated": false
}

Required fields and shared controls

Item	Proposed rule
scope	delivery:accept
required	manifestVersion, acceptedRefs, decision
tenant / project	Token and context must match; headers alone are insufficient.
idempotency	POST/PATCH: same key/body returns original result; changed body returns 409; confirm retention window.
error	code, message, requestId, correlationId, retryable, details; no sensitive data.

Continue the workflow

Two journeys, one records lifecycle

Connect paper and born-digital records through persistent identifiers, policies and evidence.

Read details

Integration quickstart

Exercise ingest → job tracking → registration → verification with synthetic data.

Read details

Integrity, provenance and evidence

Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.

Read details

Start with a verifiable scope.

Agree record classes, quality criteria, permissions and evidence before scaling.

Plan assessment