> ## 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. # Lea las transferencias de repasse CEF D+2 incluidas en una ventana > Lee el consultar-repasse-pagamentos de la red (Manual 005 v1.13 §3.4): las transferencias por registro CEF D+2 incluidas en la ventana de inclusión, cada una con su propia competencia, guía e instante de transferencia. La existencia de un registro es la liquidación: la red no publica ningún campo de estado. El mismo plazo obligatorio con un límite de 30 días que las escriturações, y la misma disciplina de no escritura: las claves del trabajo están intactas. ## OpenAPI ````yaml es/openapi/v3-current/consignado.yaml get /v1/consignado/reconciliation/repasses openapi: 3.1.0 info: contact: email: contact@lerian.studio name: Lerian Studio url: https://lerian.studio description: >- Superficie OpenAPI 3.1 para Lerian Consignado — Dataprev. API cubre las credenciales y la configuración de red de tenant, el margen de los trabajadores, las subastas y ofertas de préstamos, el registro y el ciclo de vida de los contratos, la confirmación de desembolsos, la portabilidad, la refinanciación, la renegociación, las garantías de FGTS, la conciliación, los fondos, las asignaciones, el uso, el rendimiento y las suscripciones a eventos. El material secreto se escribe en el almacén secreto tenant y ninguna operación lo devuelve nunca. license: name: Lerian Studio General License title: Lerian Consignado API version: v1.0.0 servers: - url: https://consignado.sandbox.lerian.net security: - BearerAuth: [] tags: - description: >- Custodia de credenciales de Dataprev y configuración pública del rail por tenant (carga, estado, rotación, revocación, código del solicitante y URL base del portal del trabajador) name: Credentials - description: >- Uso de la gateway del consignado en el ámbito del tenant: agregación de unidades facturables con precio por competencia name: Consignado Usage - description: >- Plano de control de suscripción al hub de streaming per-tenant (enumerar, crear, obtener, rotar, revocar y probar la entrega) name: Subscriptions - description: >- Superficie de rail de nómina Dataprev: lecturas de saldo y autorización FGTS, ejecución de garantía FGTS, suspensión de contrato, reactivación y cambios de términos, documentos de contrato propios de la red y lecturas bajo demanda de leilão solicitações, escriturações, repasses y terminaciones de empleo. name: Consignado Rail - description: >- Superficie de comando de red síncrona: las operaciones de un bancarizador sin que el prestamista conduzca sobre HTTP. Cada uno comparte su implementación de comando con el activador de evento de prestamista equivalente. name: Consignado Rail Commands - description: >- Confirmación de desembolso propiedad de la gateway: un banco cliente que registra el dinero que ya pagó a un trabajador. No cruza ninguna frontera gubernamental y no representa ninguna operación Dataprev. name: Consignado Disbursement - description: > Rendimiento de red Dataprev saliente de autoservicio per-tenant: lea y configure el requests-per-second propio de este tenant, incluida una pausa deliberada en cero name: Consignado Throughput paths: /v1/consignado/reconciliation/repasses: get: tags: - Consignado Rail summary: Lea las transferencias de repasse CEF D+2 incluidas en una ventana description: >- Lee el consultar-repasse-pagamentos de la red (Manual 005 v1.13 §3.4): las transferencias por registro CEF D+2 incluidas en la ventana de inclusión, cada una con su propia competencia, guía e instante de transferencia. La existencia de un registro es la liquidación: la red no publica ningún campo de estado. El mismo plazo obligatorio con un límite de 30 días que las escriturações, y la misma disciplina de no escritura: las claves del trabajo están intactas. operationId: listConsignadoRepasses parameters: - description: >- Inclusion window start, RFC 3339 (rail dataHoraInicio, Obrigatório Sim — Manual 005 v1.13 §3.3.1 p.20 / §3.4.1 p.26). explode: false in: query name: data_hora_inicio required: true schema: description: >- Inclusion window start, RFC 3339 (rail dataHoraInicio, Obrigatório Sim — Manual 005 v1.13 §3.3.1 p.20 / §3.4.1 p.26). examples: - '2026-07-01T00:00:00Z' format: date-time type: string - description: >- Inclusion window end, RFC 3339 (rail dataHoraFim, Obrigatório Sim). The span must not exceed 30 days — the rail answers code GR above that (Manual 005 v1.13 §4.1 p.29), and this gateway refuses 422 locally so the attempt costs no rail quota. explode: false in: query name: data_hora_fim required: true schema: description: >- Inclusion window end, RFC 3339 (rail dataHoraFim, Obrigatório Sim). The span must not exceed 30 days — the rail answers code GR above that (Manual 005 v1.13 §4.1 p.29), and this gateway refuses 422 locally so the attempt costs no rail quota. examples: - '2026-07-30T00:00:00Z' format: date-time type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/DataprevRepasseResponse' description: OK default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error security: - BearerAuth: [] components: schemas: DataprevRepasseResponse: additionalProperties: false properties: registros: description: >- The per-registro repasse records included in the window, each with its own competência. This read returns records, NOT a competência aggregate. An empty list is the rail's answer, not an error. items: $ref: '#/components/schemas/DataprevRepasseRecord' type: - array - 'null' required: - registros type: object Detail: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 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 DataprevRepasseRecord: additionalProperties: false properties: codigo_trf: description: The handle of the transfer to the financial institution. examples: - TRF00098765 type: string competencia: description: >- The registro's OWN payroll competência, yyyyMM (Manual 005 §3.4.2). It can differ from the queried window: the 21/10/2025 semantic flip changed what this field means, and data_hora_inclusao_dataprev is the disambiguator. Both are surfaced so a consumer can branch — the flip logic is NOT applied here. examples: - '202607' type: string cpf: description: >- The worker the repassed money moved for, 11 digits, re-padded from the rail's JSON Número (Manual 005 §3.4.2 p.27). A repasse whose numero_contrato matches nothing in the consumer's book is the exception this read exists to raise; without this it names nobody. Empty when the rail did not publish it. examples: - '99971699990' type: string data_hora_inclusao_dataprev: description: >- When Dataprev recorded the registro, RFC 3339 UTC. It is the disambiguator for the 21/10/2025 competência semantic flip (Manual 005 §3.4.2): branch on it together with competencia. Surfaced only; not applied here. examples: - '2026-07-17T03:12:44Z' format: date-time type: string data_hora_pagamento_guia: description: >- When the EMPLOYER paid the guia, RFC 3339 UTC (Manual 005 §3.4.2). This is the instant the §3.4 D+2 repasse deadline actually runs from — but it is only published once the repasse arrives, so a missing-repasse alarm cannot be anchored on it. Zero when the rail published none. examples: - '2026-06-02T09:00:00Z' format: date-time type: string data_repasse_if: description: >- The rail's transfer instant to the financial institution, RFC 3339 UTC (CEF D+2). examples: - '2026-07-17T00:00:00Z' format: date-time type: string id: description: >- The append-only identity of the repasse registro (Manual 005 §3.4.2) and its dedupe subject: one idempotent event is emitted per id, so at-least-once delivery and a restart re-emit are a no-op. Immutable per registro. examples: - repasse-000123456 type: string matricula: description: >- The worker's payroll registration on the bond the repassed instalment was discounted from (Manual 005 §3.4.2 p.27, Texto). Empty when the rail did not publish it. examples: - MATCEN716 type: string numero_contrato: description: >- The contract this repasse settles — the reconciliation key against the expected schedule. The SAME contract can appear in N registros. examples: - '199971600000' type: string numero_guia: description: >- The payment-guia handle. A guia paid twice yields TWO registros carrying the same numero_guia — that is money to return, and whether it is a duplicidade to claw back is the consumer's call, not the gateway's. examples: - '000000012345678' type: string status_repasse: description: >- ALWAYS EMPTY from the real rail. Manual 005 §3.4.2 publishes no situacao/PAGO/PENDENTE field on consultar-repasse-pagamentos — the mere EXISTENCE of a registro IS the liquidation, so do not wait for a status here. The key is retained only because it is a shipped cross-repo field on consignado.reconciliation.received; dropping it needs a coordinated migration. examples: - '' type: string valor_atualizacao_monetaria: description: >- Monetary restatement applied to the instalment, when any (decimal string, BRL). Absent when there is none. examples: - '3.47' type: string valor_juros_de_mora: description: >- Late-payment interest, when the rail charged any (decimal string, BRL). Absent when there is none. examples: - '11.16' type: string valor_multa: description: >- Late-payment penalty, when the rail charged one (decimal string, BRL). Absent when there is none. examples: - '22.33' type: string valor_parcela_paga: description: The instalment amount actually repassed (decimal string, BRL). examples: - '1116.31' type: string verbas_rescisorias: description: >- Marks a termination-benefit CANDIDATE, not trusted guarantee cash. It does NOT identify FGTS balance or penalty cash, recovery authority, ordering, or terminality — do not infer any of those from this flag. examples: - false type: boolean required: - id - numero_contrato - cpf - matricula - numero_guia - valor_parcela_paga - codigo_trf - data_repasse_if - data_hora_pagamento_guia - data_hora_inclusao_dataprev - status_repasse - verbas_rescisorias type: object ErrorDetail: additionalProperties: false 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 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 securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````