An application for deregistration goes out and comes back because one detail about the applicant does not fit. That is not a spectacular error, but it costs an errand, a deadline and, the second time, credibility. And it would have been detectable beforehand.
That is why a preflight comes before the notification. It is not a typo filter but the place where an application may fail without doing harm — and the submission afterwards accepts only approved content.
| Surface | Roles |
|---|---|
| Compliance | Vehicle recyclers, Dealership |
What this case requires
- An issued certificate of destruction. The preflight references case and certificate; without both there is no application.
- Details of the applicant and the registration documents. What is missing there surfaces in the preflight and not at the authority.
- A named approval for the notification. The notification carries an attestation identifier of the approving person.
- Clarity about the submission route. Exactly one adapter is currently provided,
authority_file_export: an export file for the authority, not a direct connection into its procedure.
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 |
|---|---|---|
| Preflight the application | POST /compliance/deregistration-applications/preflight | applicationMode, applicant and registrationDocuments are checked before anything leaves |
| Create the notification | POST /compliance/authority-notifications | adapterType and obligationParties; approvalAttestationId names the approving person |
| Submit | POST /compliance/submissions | Only approved content is submitted — schemaVersion and attestation belong to the call |
Why each stage is needed
- Preflight the application.
POST /compliance/deregistration-applications/preflighttakes case, certificate, application mode, the obligated parties, the applicant and the registration documents. The response names blockers under the stored rule set, without anything reaching the authority. - Create the notification.
POST /compliance/authority-notificationstakes subject, adapter type, the obligated parties plus approval time and attestation identifier. The notification is thereby attributed to a person before it goes anywhere; only a signed-in person with a re-confirmed login may create it. - Submit.
POST /compliance/submissionstakes the adapter type — currently exactlyauthority_file_export—, the schema version1.0.0, the approval’s attestation identifier and the reference to the notification. Only approved content is therefore submitted; a submission without approval is not provided for in the contract.
curl -X POST \
-H 'X-Api-Key: <API_KEY>' \
-H 'X-Compliance-Organisation-Id: <ORGANISATION>' \
-H 'Idempotency-Key: uebermittlung-2026-09-12-017' \
-H 'Content-Type: application/json' \
-d '{"adapterType":"authority_file_export","schemaVersion":"1.0.0","approvedByAttestationId":"<attestationId>","authorityNotificationId":"<authorityNotificationId>"}' \
'https://api.tapinomahub.com/compliance/submissions'What you end up with
What remains is a submission with a state, attributable to a person and an approval — and an application that does not fail on a detail which was visible beforehand.
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
What do I do with a blocker from the preflight?
Resolve it. The blocker names code and message, where applicable a requirementId; afterwards the preflight can be repeated without anything having happened at the authority.
Can I submit without a notification?
No. The submission takes the reference to the notification and the approval’s attestation identifier. That is the stop which prevents unfinished content from going out.
Does the submission’s state mean the authority agreed?
No. It describes our process. The authority decides on approval in its own procedure.