Close an indeterminate send by hand
Records an operator’s finding on an INDETERMINATE send — the engine’s settle or revert, JD support’s written answer — with the evidence and a note, and changes nothing else. It is a record, never a routing decision: the outcome stays INDETERMINATE, a second send of the same control id is still refused, and the engine’s ConsultaNumCtrlIF is still forwarded to JD, whose answer may still resolve the row. It never resends and calls no vendor. The Courier offers no by-hand NOT_SENT: an operator wrong about “never sent” would release the control id for a second send, and two TEDs would reach BACEN. What the close changes is the alert: a closed send stops aging. 409 JDC-0303 when the send is not INDETERMINATE or was already closed; 404 JDC-0302 when the journal does not hold it. A body missing a field, carrying a non-string or an unexpected property is 400 JDC-0001; a present field whose value breaks a rule (blank evidence, a note outside 10-500 characters after trimming) is 422 JDC-0002.
Authorizations
JWT bearer token issued by the identity provider.
Headers
Idempotency key; a retry with the same key and body replays the first answer.
Path Parameters
256Body
Response
OK
spb An operator's by-hand close; null unless one was recorded. A record only: the outcome is unchanged.
Originating engine; this field routes the SPB return leg.
DETERMINED, INDETERMINATE, RESOLVED, NOT_SENT The engine's ConsultaNumCtrlIF trail for this send; null until the first.
How the vendor's own answer settled an indeterminate send; null until it did.
Present while the outcome is INDETERMINATE: seconds since the send left, growing, for an open send; frozen at closedAt minus sentAt once an operator closed it by hand, because a closed send no longer ages for the alert.

