Submit correction intake
Write one corrected Start-section answer inside an open session (AUD-376).
Mirrors submit_correction_response step for step: same visibility check, same lock order, same session lookup and codes. The field is resolved in the FROZEN snapshot's Start definition only. The database guards (enforce_intake_lock, log_intake_revision) fire on the update below, which runs on this caller's RLS connection, so the opener rule and the history row hold for any other door too.
Authorization
OrgApiKey Organization API key. Send as Authorization: Bearer <key>. Create one in Admin > Settings > API keys.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
One corrected Start-section answer inside an open correction session (AUD-376).
One addressed answer per call, never a merge map: a group's value is a whole array, so a merge of one member would rewrite every entry and race a second edit of another entry.
Response Body
application/json
application/json
curl -X PATCH "https://api.auditmark.io/v1/inspections/497f6eca-6276-4993-bfeb-53cbbbba6f08/corrections/497f6eca-6276-4993-bfeb-53cbbbba6f08/intake" \ -H "Content-Type: application/json" \ -d '{ "field_key": "string" }'{ "field_key": "string", "group_key": "string", "entry_index": 0, "value": null, "intake": {}}{ "detail": [ { "loc": [ "string" ], "msg": "string", "type": "string", "input": null, "ctx": {} } ]}