reconciliation

Retry Bank Statement Import

Re-queue a failed bank-statement import for re-processing (recover by id).

No body — the staged sha256 bytes persist. CompanyMember, scoped via the loaded row (404 missing / 403 out of scope). failed → pending (202); pending/processing → returned as-is (idempotent); done → 409.

Accountant/owner (ZCT-257): a retry re-runs the extractor, which is a billed analysis and lands entries in the books. The row is resolved here rather than only inside the service because the gate needs its company_id first.

post/bank-statement-imports/{import_id}/retry

Request

Base URL: https://app.zeno-works.ch (the document declares no server; this is the origin it was published from)
URL: https://app.zeno-works.ch/bank-statement-imports/{import_id}/retry
Auth: none declared

Path parameters

import_idstring required

Headers

authorizationstring nullable

Cookies

access_tokenstring nullable

Response

Successful Response

idstring required

company_idstring required

sha256string required

filenamestring required

content_typestring nullable

sizeinteger nullable

uploaded_bystring nullable

status'pending' | 'processing' | 'done' | 'failed' required

Async-processing lifecycle of an uploaded non-CAMT bank statement.

Mirrors :class:AccountingDocumentStatus (its own dedicated Postgres enum type bank_statement_import_status): pending (enqueued) → processing (claimed by the BankStatementImportWorker) → done / failed.

errorstring nullable

result_summaryobject nullable

statements_createdinteger required

entries_createdinteger required

created_atstring date-time required

processed_atstring date-time nullable

Changes

No recorded changes to this operation across all 1 revision of this API.