Auditmark

Close correction

POST
/inspections/{inspection_id}/corrections/{correction_id}/close

Finish a correction: validate, restore the status and the participant row, then regenerate the report.

The validation, the restore and the close itself are one transaction. The regeneration is NOT part of it and is not claimed to be: it is queued to run after the commit, best-effort (see the comment at the append below).

Deliberately NOT advance_inspection. That endpoint enqueues the web-first report email, emits inspection.completed and notifies participants, so reusing it would re-mail the client and re-announce a completion on EVERY correction. Its validator is reused; its side effects are not.

Authorization

OrgApiKey
AuthorizationBearer <token>

Organization API key. Send as Authorization: Bearer <key>. Create one in Admin > Settings > API keys.

In: header

Path Parameters

inspection_id*Inspection Id
correction_id*Correction Id

Response Body

application/json

application/json

curl -X POST "https://api.auditmark.io/v1/inspections/497f6eca-6276-4993-bfeb-53cbbbba6f08/corrections/497f6eca-6276-4993-bfeb-53cbbbba6f08/close"
null
{  "detail": [    {      "loc": [        "string"      ],      "msg": "string",      "type": "string",      "input": null,      "ctx": {}    }  ]}