Skip to main content
POST
/
v1
/
transfers
/
ted-in
/
replay
Replay TED IN Backlog
curl --request POST \
  --url https://plugin-br-bank-transfer.sandbox.lerian.net/v1/transfers/ted-in/replay \
  --header 'Authorization: Bearer <token>' \
  --header 'X-Idempotency: <x-idempotency>' \
  --header 'X-Organization-Id: <x-organization-id>'
{
  "tenantId": "11111111-1111-1111-1111-111111111111",
  "outcome": "success",
  "replayed": 2
}

Documentation Index

Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

JWT Bearer token authentication. The token must include a tenantId claim that matches the X-Organization-Id header.

Headers

​
X-Organization-Id
string<uuid>
required

Organization ID used as the tenant identifier. All data is scoped to this organization. Must match the JWT tenantId claim when authentication is enabled.

​
X-Idempotency
string
required

Required idempotency key for safe retries. Use a UUID v4 or unique business identifier. 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.

Maximum string length: 255

Response

Indicates that the replay pass completed. The outcome field reports the cycle result and replayed is the number of backlog rows reprocessed.

​
tenantId
string<uuid>
required

The tenant for which the replay pass ran.

Example:

"11111111-1111-1111-1111-111111111111"

​
outcome
enum<string>
required

Replay outcome label.

Available options:
success,
empty,
skipped_outside_window,
skipped_busy,
cancelled,
error
Example:

"success"

​
replayed
integer
required

Number of persisted backlog rows reprocessed during this pass.

Required range: x >= 0
Example:

2