The certificate is often treated as a final step: the vehicle is recycled, so fill in the form. An audit then asks who approved it, when it was issued and whether the keeper actually received the document — and a printout without that chain answers none of these.
The certificate is therefore not a form here but a sequence of events with separated responsibilities: draft, approval by a named person, preparation of the print set, issuance and delivery. Every stage is evidenced individually.
| Surface | Roles |
|---|---|
| Compliance | Vehicle recyclers |
What this case requires
- A case in which the vehicle is determined end-of-life. Without a status determination the certificate lacks its basis.
- A recognised issuing site. The draft names it in
issuerFacilityId; issuer and acting person are derived by the server from the login, not from the call. - A person authorised to sign. The approval is attributed to a person, not to the facility in general.
- A decision on the route. Electronic or as a German paper certificate — each has its own call.
The sequence
The table names the responsible call per stage and what exists afterwards. The reasoning for why a stage cannot be skipped follows below it.
| Stage | Call | What exists afterwards |
|---|---|---|
| Create the draft | POST /compliance/cases/{id}/certificates | legalProfile and issuerFacilityId — rule set and issuing site |
| Approve | POST /compliance/certificates/{id}/approve | attestationId identifies the person who approved — not the system |
| Prepare the print set | POST /compliance/certificates/{id}/prepare-print | renderProfile and copySetReference for the official form set |
| Issue | POST /compliance/certificates/{id}/issue-electronic | signatureEnvelopeId and serializationVersion; the paper route has its own call |
| Deliver | POST /compliance/certificates/{id}/deliveries | recipientPartyId, medium and deliveredAt — delivery is itself an event |
Why each stage is needed
- Create the draft.
POST /compliance/cases/{id}/certificatestakeslegalProfileandissuerFacilityId— the rule set and the issuing site. A draft is not yet a certificate — which is exactly why it exists. - Approve.
POST /compliance/certificates/{id}/approvecarriesapprovedAtand an attestation identifier. This stage is the core of auditability: it identifies the person who approved. A system approves nothing, and accordingly the contract requires a signed-in person who has re-confirmed their login; an API key alone is not enough. - Prepare the print set.
POST /compliance/certificates/{id}/prepare-printtakes a render profile and a copy-set reference. The official form has several copies; which copy goes where is part of the duty and not a question for the printer. - Issue.
POST /compliance/certificates/{id}/issue-electroniccarries the signature envelope and serialisation version. For the paper route there is a dedicated call,POST /compliance/certificates/{id}/issue-de-paper, recording the place of issue and the four original copies — two routes, one state. - Deliver.
POST /compliance/certificates/{id}/deliveriescarries recipient, medium and delivery time. Delivery is itself an event, because “issued” and “arrived with the keeper” are two different facts.
curl -X POST \
-H 'Cookie: __Host-tapinomahub_session=<SITZUNG>' \
-H 'X-CSRF-Token: <CSRF_TOKEN>' \
-H 'X-Compliance-Organisation-Id: <ORGANISATION>' \
-H 'If-Match: "<etag>"' \
-H 'Idempotency-Key: freigabe-2026-09-12-017' \
-H 'Content-Type: application/json' \
-d '{"approvedAt":"2026-09-12T10:15:00Z","attestationId":"<attestationId>"}' \
'https://api.tapinomahub.com/compliance/certificates/<id>/approve'What you end up with
In the end an issued certificate exists whose path from approval through issuance to the recipient is evidenced. In an audit the question “who approved this” is no longer research but a field.
Where to find this in the documentation
The binding field lists, error codes and sample responses live in this surface’s OpenAPI contract at docs.tapinomahub.com (tapinoma-compliance). All use cases arranged by surface and role: overview of the use cases.
Sources and legal references
Frequently asked
Do I need the draft if I already have the data?
Yes. The contract provides no other entry point: approval, print preparation and issuance start from the previously created draft. Approval and issuance are separate from it.
Paper or electronic?
Both are provided for, each with its own call. The paper route records place of issue and number of originals, the electronic one the signature envelope.
Why is delivery a separate call?
Because issuance and delivery are different facts. An issued certificate that never reaches the keeper is an open case.