← Technical API reference

Frontend module · STATIC DECLARATIONS

Payment Reconciliation Api client API reference · mansoq-web

6 client route/call declarations with path parameters, named payload/response types and source references. Exact server acceptance and permissions require the matched backend contract.

Static API contract — behavior review pending. Source baseline f6e9f05f76d4.

Enable JavaScript to inspect structured operation, parameter, schema and permission evidence. Download this reference and its evidence.

Client contract scope

These 6 declarations come from repositories/platform/mansoq-web/src/types/billing/paymentReconciliation/paymentReconciliationApi.ts. Client types and noAuth flags describe the caller; they do not authorize a server action. Dynamic paths and missing backend matches are retained as review work, not repaired into invented endpoints.

Operation map

Client method HTTP method Path pattern Resolution
default.listPaymentReconciliation GET /api/v1/facility/{facilityId}/payment_reconciliation/ literal
default.retrievePaymentReconciliation GET /api/v1/facility/{facilityId}/payment_reconciliation/{paymentReconciliationId}/ literal
default.createPaymentReconciliation POST /api/v1/facility/{facilityId}/payment_reconciliation/ literal
default.updatePaymentReconciliation PUT /api/v1/facility/{facilityId}/payment_reconciliation/{paymentReconciliationId}/ literal
default.cancelPaymentReconciliation POST /api/v1/facility/{facilityId}/payment_reconciliation/{paymentReconciliationId}/cancel_payment_reconciliation/ literal
default.changeAccount POST /api/v1/facility/{facilityId}/payment_reconciliation/change_account/ literal

default.listPaymentReconciliation

GET /api/v1/facility/{facilityId}/payment_reconciliation/. typed route object; literal. multiple static method/path matches across source registrations; installed target and boundary require review.

Path parameters: facilityId. Transport strings are declared here; semantic identifier types require the server contract.

response type: PaginatedResponse<PaymentReconciliationBase>. client-side declaration; not proof of accepted server payload.

PaginatedResponse declared fields:

Field Type Required Description
count number true —
results TItem[] true —

PaymentReconciliationBase declared fields:

Field Type Required Description
id string true —
reconciliation_type PaymentReconciliationType true —
status PaymentReconciliationStatus true —
kind PaymentReconciliationKind true —
issuer_type PaymentReconciliationIssuerType true —
outcome PaymentReconciliationOutcome true —
disposition string false —
payment_datetime string false —
method PaymentReconciliationPaymentMethod true —
reference_number string false —
authorization string false —
tendered_amount string false —
returned_amount string false —
note string false —
amount string true —

Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.

default.retrievePaymentReconciliation

GET /api/v1/facility/{facilityId}/payment_reconciliation/{paymentReconciliationId}/. typed route object; literal. multiple static method/path matches across source registrations; installed target and boundary require review.

Path parameters: facilityId, paymentReconciliationId. Transport strings are declared here; semantic identifier types require the server contract.

response type: PaymentReconciliationRead. client-side declaration; not proof of accepted server payload.

PaymentReconciliationRead declared fields:

Field Type Required Description
target_invoice InvoiceList true —
account AccountRead true —
is_credit_note boolean true —
location LocationRead | null true —
created_by UserReadMinimal true —
updated_by UserReadMinimal true —
created_date string true —
modified_date string true —
extensions Record<string, Record<string, unknown>> false —

Composed/inherited schema references: PaymentReconciliationBase. Exact generic composition is retained in the structured reference and requires server-side confirmation.

Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.

default.createPaymentReconciliation

POST /api/v1/facility/{facilityId}/payment_reconciliation/. typed route object; literal. multiple static method/path matches across source registrations; installed target and boundary require review.

Path parameters: facilityId. Transport strings are declared here; semantic identifier types require the server contract.

request type: PaymentReconciliationCreate. client-side declaration; not proof of accepted server payload.

PaymentReconciliationCreate declared fields:

Field Type Required Description
target_invoice string false —
account string true —
is_credit_note boolean false —
location string false —
extensions Record<string, Record<string, unknown>> false —

Composed/inherited schema references: PaymentReconciliationBase. Exact generic composition is retained in the structured reference and requires server-side confirmation.

response type: PaymentReconciliationRead. client-side declaration; not proof of accepted server payload.

Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.

default.updatePaymentReconciliation

PUT /api/v1/facility/{facilityId}/payment_reconciliation/{paymentReconciliationId}/. typed route object; literal. multiple static method/path matches across source registrations; installed target and boundary require review.

Path parameters: facilityId, paymentReconciliationId. Transport strings are declared here; semantic identifier types require the server contract.

request type: PaymentReconciliationUpdate. client-side declaration; not proof of accepted server payload.

Composed/inherited schema references: PaymentReconciliationBase. Exact generic composition is retained in the structured reference and requires server-side confirmation.

response type: PaymentReconciliationRead. client-side declaration; not proof of accepted server payload.

Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.

default.cancelPaymentReconciliation

POST /api/v1/facility/{facilityId}/payment_reconciliation/{paymentReconciliationId}/cancel_payment_reconciliation/. typed route object; literal. multiple static method/path matches across source registrations; installed target and boundary require review.

Path parameters: facilityId, paymentReconciliationId. Transport strings are declared here; semantic identifier types require the server contract.

request type: PaymentReconciliationCancel. client-side declaration; not proof of accepted server payload.

PaymentReconciliationCancel declared fields:

Field Type Required Description
reason PaymentReconciliationStatus true —

response type: PaymentReconciliationRead. client-side declaration; not proof of accepted server payload.

Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.

default.changeAccount

POST /api/v1/facility/{facilityId}/payment_reconciliation/change_account/. typed route object; literal. multiple static method/path matches across source registrations; installed target and boundary require review.

Path parameters: facilityId. Transport strings are declared here; semantic identifier types require the server contract.

request type: object. client-side declaration; not proof of accepted server payload.

default.changeAccount.request declared fields:

Field Type Required Description
target_account string true —
payment_reconciliations string[] true —

response type: void. client-side declaration; not proof of accepted server payload.

Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.

Pinned source evidence

Links require access to the private source repository.