MUmultigest
Financeiro (Protected)

Liquidar parcialmente um movimento pendente

Changed on

Settle part of a pending movement — or all of what is left of it.

#764 v2: the payment becomes its OWN paid movement (its date, its account) and the pending one shrinks to what is still owed, in one locked transaction — see app/services/partial_settlements.py. A losing race, a stale expected_remaining or a disabled kill switch is a 409 (reload, do not correct the input); bad input is a 400.

Plain def — synchronous pyodbc must not run on the event loop.

post/api/financeiro/movements/{movement_id}/settle-partial

Request

  • Base URL
    https://api.multigest.pt (the document declares no server; this is the origin it was published from)
  • URL
    https://api.multigest.pt/api/financeiro/movements/{movement_id}/settle-partial
  • Auth
    API key in header x-api-token and API key in header x-origin-verify

Path parameters

movement_idinteger required

Headers

x-api-tokenstring nullable

Request body

amountnumber required

Valor a liquidar agora (positivo)

payment_method_idinteger required

Conta / método de pagamento usado

expected_remainingnumber nullable

Valor em falta que o utilizador estava a ver

Response

Successful Response

unknown required

Changes