Repair reviewed ledger projections
POST
/api/companies/{companyId}/accounting/repairPersonal API keyConsole session
Repair reviewed ledger projections.
Requires an audit reason and the current inspection fingerprint. A stale inspection returns 409. Missing evidence is never invented. Organization-scoped board write access is required; viewers and agents cannot mutate accounting.
Authorization
Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.
Path parameters
companyIdstringRequiredThe organization's id.
Request body
application/json · required
fingerprintstringRequired
pattern: ^[a-f0-9]{64}$reasonstringRequired
1–1000 charactersResponses
200SuccessThe request worked; the body holds the result.
400Bad requestThe request is malformed or failed validation.
details names each field that failed.401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.
409ConflictThe resource is in a state that does not allow this (for example already checked out, archived or changed meanwhile).
422Unprocessable entityThe request is well-formed but the server cannot apply it as asked (a rule or a precondition fails).
Errors return {"error": "..."}, often with a code and details. See errors and limits.