Trigger an on-demand reconciliation run
Starts a reconciliation cycle on demand. This is the same cycle that the worker runs periodically: it queries the rail about the transfers in AWAITING_RECONCILIATION and applies the conclusive outcomes. Use it after a rail outage, or when operations do not want to wait for the next cycle.
The response is 202 with the runId of the scheduled cycle. Processing is asynchronous, and its effects appear in the transfers and in the operations queue. Only one cycle runs at a time: if a cycle is already running, the response is 409 TED-0015.
X-Idempotency is required (no body). Check X-Idempotency-Replayed in the response to tell a new cycle from a replay.
Autorizações
JWT token that the Lerian Access Manager issues for your institution. Send it in Authorization: Bearer <token> on every call (except the public health probes). The tenant never comes from the body, the query, or the path. Each operation requires a role with the matching permission (see the API overview). Without it, 403 TED-0071. Missing, invalid, or expired token: 401 TED-0070.
Cabeçalhos
Replay window of the idempotency key, in seconds. Default 300 (5 minutes) when missing or invalid. Values outside 30 s to 7 days are adjusted to these limits. Only the value of the FIRST request for a key counts. A change to X-TTL on retries has no effect. The window sets how long the response is replayed.
x >= 1Idempotency key that the integrator creates (1 to 128 printable ASCII characters, no spaces; we recommend a UUID). Required on every operation with an effect. Send the SAME key again when you retry a call that failed because of a timeout or network error. Same key + same body returns the original response with X-Idempotency-Replayed: true and no new effect. Same key + different body responds 422 TED-0012. Same key still in processing responds 409 TED-0013 (retry after Retry-After). Missing or in the wrong format: 400 TED-0011.
Correlation identifier of this request (UUID). Optional: when you omit it, or when the value is not a well-formed UUID, the platform creates a UUID and returns it in the X-Request-Id header of the response. The resolved identifier goes to the logs, spans, and audit events of this request. Keep it to open a support ticket.
Resposta
Run scheduled. runId identifies the cycle. If X-Idempotency-Replayed: true, this is the replay of an earlier trigger.
Reconciliation run scheduled on demand. Processing is asynchronous; track the effects in the queues and in the affected resources.

