A repair calculation is a dense document: line items, labour values, part numbers, equipment. As a PDF it is readable for a person and worthless to a system. Retyping it transfers errors; ignoring it discards the most reliable description of the damage that exists.
The chain deliberately separates two sources: the document says what was calculated, the photos say what is visible. Both belong in the same file but not in the same field — otherwise you cannot later tell what was measured from what was described.
| Surface | Roles |
|---|---|
| Hub | Experts and insurers, Workshop, Vehicle trading |
What this case requires
- The calculation as a retrievable document. A photographed printout works too — the hit rate simply falls with the resolution.
- Photos of the damage if a description is wanted. No image, no description; nothing is estimated.
- The entitlement to transmit. Calculations routinely contain names, plates and insurance data.
- A decision on what the file serves. Residual value assessment counts different fields than dismantling planning.
- The entitlement to query the vehicle. With the call you confirm that you are the keeper, the owner or demonstrably authorised or otherwise legally entitled, and that you use the identification number solely for the stated permissible purpose.
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 |
|---|---|---|
| Read the calculation | POST /scanner/document/calculation | Line items, labour values and equipment as structure instead of a PDF |
| Pull the vehicle data | POST /scanner/document/vehicle | Vehicle and equipment from the same document, without retyping |
| Describe the damage | POST /vision/damage/describe | A description of what the photos show — and no more |
| Grade the component | POST /vision/part/quality | A quality grade per component as the basis for reuse or replacement |
Why each stage is needed
- Read the calculation.
POST /scanner/document/calculationtakes the document atfileUrlin the only provided level,standard, and returns line items, labour values and equipment as structure. This is the step with the greatest leverage: it replaces the manual work nobody otherwise does. - Pull the vehicle data.
POST /scanner/document/vehicletakes vehicle and equipment from the same document. A separate call, because not every file needs calculation depth — some need only the vehicle. - Describe the damage.
POST /vision/damage/describedescribes what the photos show. This stage complements the calculation, it does not correct it: a calculated replacement and a visible scratch are two statements. - Grade the component.
POST /vision/part/qualityreturns a quality grade per component. Only then can you decide what is reused and what is replaced — the calculation alone does not answer that.
curl -X POST \
-H 'X-Api-Key: <API_KEY>' \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: schaden-2026-0871-kalkulation' \
-d '{"fileUrl":"https://example.com/kalkulation.pdf","quality":"standard"}' \
'https://api.tapinomahub.com/scanner/document/calculation'What you end up with
What remains is a file in which calculated line items, vehicle data and visible condition are separately traceable. For the assessor that is the basis of the valuation, for the recycler the basis of dismantling planning.
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-hub). All use cases arranged by surface and role: overview of the use cases.
Sources and legal references
Frequently asked
Can I submit a multi-page calculation?
The binding statements on format and size live in the OpenAPI contract. Resolution matters in any case: what is not legible in the image is not in the response.
Why are there two calls for the same document?
Because not every file needs the same depth. If you only want the vehicle and its equipment, you use POST /scanner/document/vehicle instead of the calculation call.
May I copy the damage description into a listing?
You may use it as a basis. Responsibility for the statements in the listing stays with you — the description describes the visible and warrants no condition.