> ## 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. # Timeline of the incoming TED transitions > Returns the timeline of an incoming TED: one entry for each status transition, in chronological order. Each entry has the time, the source and target states, who caused the transition (`origin`), and the related identifier (for example, the `nuop` or the rail event ID). Use it for customer support and audit, especially to explain why a TED went to manual review or was returned. For the current state, `GET /v1/incoming-transfers/{incomingTransferId}` is enough. ## OpenAPI ````yaml /en/openapi/v3-current/ted-lerian.yaml get /v1/incoming-transfers/{incomingTransferId}/timeline openapi: 3.1.0 info: description: >- API of **TED Lerian**, the interface over Lerian SPB. Your institution uses it to send TEDs, make internal transfers, track incoming TEDs, and operate returns, queues, and policy on its Midaz ledger. The [API overview](/en/reference/interfaces/ted-lerian/ted-lerian-api-overview) gives the concepts, the roles, and the conventions. title: TED Lerian API version: v1.0.0 servers: - url: https://api.example.com description: >- Replace the example host with the URL provided during environment onboarding. security: - BearerAuth: [] tags: - description: >- Outgoing TEDs and internal transfers: fee quote, creation, query, timeline, and cancellation. Every integration starts here. name: Transfers - description: >- Incoming TEDs from other institutions: query, timeline, and operator actions (full return and manual review resolution). name: Incoming Transfers - description: >- STR participant list, to resolve COMPE code ↔ ISPB and validate the destination bank before you create a transfer. name: Participants - description: >- Back office: operations queue, inconsistency findings between the ledger and the STR, reviews of rail facts, held returns, and manual unblock with evidence. name: Reconciliation - description: >- Operations dashboard: daily aggregates, regulatory deadlines (30/60/60 min), and the closing balance that the STR reported. name: Operations - description: >- Institution configuration (editor): operating window and cut-off, usage limits, holiday calendar, and ISPB → organization bindings. name: Policy paths: /v1/incoming-transfers/{incomingTransferId}/timeline: get: tags: - Incoming Transfers summary: Timeline of the incoming TED transitions description: >- Returns the timeline of an incoming TED: one entry for each status transition, in chronological order. Each entry has the time, the source and target states, who caused the transition (`origin`), and the related identifier (for example, the `nuop` or the rail event ID). Use it for customer support and audit, especially to explain why a TED went to manual review or was returned. For the current state, `GET /v1/incoming-transfers/{incomingTransferId}` is enough. operationId: getIncomingTransferTimeline parameters: - description: Identifier of the incoming TED in: path name: incomingTransferId required: true schema: description: Identifier of the incoming TED format: uuid type: string - $ref: '#/components/parameters/XRequestId' responses: '200': content: application/json: example: entries: - at: '2026-10-22T14:10:03Z' origin: RAIL reference: '87654321202610220000123' toStatus: RECEIVED - at: '2026-10-22T14:10:09Z' fromStatus: RECEIVED origin: LEDGER toStatus: CREDITED resourceId: a7d3e9f1-2b4c-4d6e-8f0a-1b3c5d7e9f0a schema: $ref: '#/components/schemas/IncomingTimelineDTO' description: Timeline in chronological order, from receipt to the current status. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '401': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: 'Not authenticated: token missing, invalid, or expired (`TED-0070`).' headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '403': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- No permission: the token's role does not authorize this action, or the product license is not valid for the organization (`TED-0071`). headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '404': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Resource does not exist in this institution, or the identifier is not in UUID format (`TED-0010`). headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Parameter outside the declared format (for example, a `date` that is not YYYY-MM-DD): framework validation, with no TED code. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Unexpected failure (`TED-9000`). If it continues, contact support and give the `X-Request-Id` of the response. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' '503': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Organization scope not configured for this installation (`TED-0080`): the read fails closed until the configuration exists. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' components: parameters: XRequestId: description: >- 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. in: header name: X-Request-Id schema: format: uuid type: string schemas: IncomingTimelineDTO: additionalProperties: false description: >- Timeline of an incoming TED: each entry is a status transition with origin, timestamp, and related reference. properties: entries: description: Transitions in chronological order. items: $ref: '#/components/schemas/IncomingTimelineEntryDTO' type: array resourceId: description: Identifier of the incoming TED. format: uuid type: string required: - resourceId - entries type: object Detail: additionalProperties: true description: >- Standard error body (RFC 9457, `application/problem+json`) for every `/v1` operation. Use `code` (TED-NNNN) to handle the error in code, `detail` for the readable message, and `errors` for the invalid fields of a 422. The `X-Request-Id` of the response identifies the occurrence for support. properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. type: object IncomingTimelineEntryDTO: additionalProperties: false description: >- A status transition of the incoming TED. `origin` tells you what caused it (API, rail, STR, ledger, worker, operator, or system). properties: actor: description: Operator identity when origin=OPERATOR. type: string at: description: Instant (UTC) of the transition. format: date-time type: string fromStatus: description: IncomingTransferStatus value; absent in the first transition. type: string origin: enum: - API - RAIL - STR - LEDGER - WORKER - OPERATOR - SYSTEM type: string reason: description: Official reason for the transition, verbatim. type: string reference: description: Related identifier (nuop, numCtrlStr, event id). type: string toStatus: description: IncomingTransferStatus value. type: string required: - at - toStatus - origin type: object ErrorDetail: additionalProperties: false description: >- An invalid field inside a validation error: where it is (`location`), what is wrong (`message`), and the value received. properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object Upstream: additionalProperties: false description: >- Error reported by an upstream system (ledger or rail), when the service chooses to expose it. Absent in most errors. properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object headers: XRequestId: description: >- Echo of the request X-Request-Id: the value that the client sent, or the UUID that the platform generated when the client sent none. Present in every response, success or error. schema: format: uuid type: string securitySchemes: BearerAuth: bearerFormat: JWT description: >- JWT token that the Lerian Access Manager issues for your institution. Send it in `Authorization: Bearer ` 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`. scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.