Close TED IN Reconciliation Gaps
Use this endpoint to close every open TED IN reconciliation gap whose latch time falls in a window, after a person checked the JD ExtratoFinanceiro statement and found no message lost in that window. The automatic poller recovery clears the latch but leaves its gap open, because it does not prove that nothing was lost. This endpoint closes those gaps.
No money moves here. The note records a check done outside this system. latchedTo must not be in the future, and latchedFrom must not be after it. Equal bounds close one gap. The answer is the number of gaps closed, and it can be zero.
This is a tenant-wide administrative action. It requires the transfers:resolve permission and a user token. It does not require the X-Organization-Id header. In multi-tenant deployments it is scoped to the caller’s resolved tenant database.
Autorizações
JWT Bearer token authentication. The tenantId is derived from the bearer token or authenticated request context and is not supplied through X-Organization-Id.
Cabeçalhos
Required idempotency key for safe retries. Use a UUID v4 or a unique business identifier, made of letters, digits, ., _, and -. If the same key is sent again and the original request was already processed, the cached response is returned.
See Retries and idempotency for details.
255^[a-zA-Z0-9._-]+$Corpo
The window of latch times to close, and the note that records the check.
The start of the window of latch times, inclusive.
"2026-10-01T00:00:00Z"
The end of the window of latch times, inclusive. It must not be in the future.
"2026-10-31T23:59:59Z"
The justification of the person who checked the statement.
10 - 500"JD ExtratoFinanceiro checked: no message lost in October"
Resposta
Indicates that the open gaps in the window were closed.
The number of gaps closed. It can be zero.
293

