Acceptance Protocol Schema
Felder
Acceptance Protocol Schema
Schema for validating project acceptance protocol (Abnahmeprotokoll) entities
projectId
Project this acceptance protocol belongs to
protocolNumber
Human-readable sequence number (e.g. ABN-2026-00042). Assigned server-side; protected.
title
Protocol title (defaults to "Abnahmeprotokoll – <project title>")
status
Lifecycle status. DRAFT = editable; SENT = envelope dispatched/awaiting signature; SIGNED = customer accepted; REJECTED = customer declined; CANCELLED = voided. Protected.
DRAFTSENTSIGNEDREJECTEDCANCELLEDintroText
Editable protocol body / project description shown to the customer.
projectSnapshot
Immutable copy of the relevant project fields at protocol creation time, so the protocol stays stable even if the project changes afterwards. Protected.
projectNumber
title
description
startDate
endDate
managerName
partyName
partyAddress
signerName
Name of the customer signer.
signerEmail
Email of the customer signer (used for the magic-link flow).
signerPartyId
Customer party/contact UUID of the signer.
coSignerUserId
Optional internal user (e.g. project manager) who co-signs.
feedback
Free-text feedback the customer enters during acceptance.
envelopeId
Linked sign_envelope that drives the signature workflow. Protected.
unsignedPdfFileId
Generated, not-yet-signed protocol PDF (files collection). Protected.
signedPdfFileId
Final signed protocol PDF (files collection). Protected.
sentAt
When the protocol was sent for signature. Protected.
acceptedAt
When the customer signed. Protected.
acceptedVia
How the signature was collected. Protected.
IN_PERSONMAGIC_LINKnullipAddress
Forensic: signer IP at acceptance time. Protected.
userAgent
Forensic: signer user-agent at acceptance time. Protected.
rejectionReason
Reason given when the customer rejects the protocol. Protected.
Keine Felder passen zum Filter.
Standard-Endpoints
Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:
GET /api/v1/acceptance_protocols— Liste, paginiert + filterbarGET /api/v1/acceptance_protocols/<id>— Einzelne EntityPOST /api/v1/acceptance_protocols— AnlegenPATCH /api/v1/acceptance_protocols/<id>— Teil-UpdateDELETE /api/v1/acceptance_protocols/<id>— Soft-DeleteGET /api/v1/acceptance_protocols/<id>/timeline— Audit + Aktivitäten