> ## 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. # Record the human treatment of a parked STA event > Writes the audit record that answers the three-day dead-letter window: which parked record, from which direction, under which parking token, and what the operator did about it (replayed, recorded, escalated). It does NOT remove anything: the dead-letter destination is the Kafka topic lerian.streaming.br-sisbajud.dlq, a LOG with its own retention, so a treated record stays exactly where it is and this acknowledgement — not the record's absence — is what says it was handled. Replaying means seeking the consumer group back to the source offset the record's headers name. Answers with a receipt id for the ticket. 422 when the parking token is not one the consumer emits, when the action is unknown, or when institutionId or eventId are missing — the refusal carries a code and a canned detail, so the valid tokens are published as this request's reason enum rather than named in the answer. ## OpenAPI ````yaml /es/openapi/v3-current/sisbajud.yaml post /admin/sta-dlq/{eventId}/acknowledge openapi: 3.1.0 info: description: >- API for Lerian SISBAJUD — the participant-side rail that integrates the institution with Banco Central do Brasil's SISBAJUD (Sistema de Busca de Ativos do Poder Judiciário) system for judicial asset blocking and unblocking. It covers judicial-order administration, remittance and return file management, reconciliation, SLA monitoring, LGPD data-subject requests, and per-institution configuration and connector credentials. title: Lerian SISBAJUD API version: 1.0.0 servers: - url: https://sisbajud.sandbox.lerian.net security: - BearerAuth: [] tags: - description: >- Institution configuration lifecycle: create (with key provisioning), read, and partial update of a connector configuration addressed by institution id. name: Institution - description: >- LGPD data-subject access, portability, resolution, and cryptographic erasure operations, addressed by institution id. name: LGPD - description: >- Manual cryptographic key administration: KEK and tokenization-keyset rotation for an institution, addressed by institution id. name: Security - description: >- Judicial-order operational resilience write operations, such as reprocessing a FAILED order, addressed by institution id. name: Order Operations - description: >- Non-compliance-log administration, such as registering an SLA-breach justification, addressed by institution id. name: Non-Compliance - description: >- Manual reconciliation administration, such as triggering an on-demand reconciliation run. name: Reconciliation - description: >- Authenticated remittance-file reception: a caller notifies the service of a file already present in the inbound bucket and the service runs the receive and parse pipeline. name: Remittance File - description: >- Return (response) file administration, such as forcing an on-demand return-file generation outside the scheduled cron. name: Return File - description: >- Administrative operations: return-file content retrieval, monitoring close, and unblock execution. A deployment serves them only when it is configured for local or development use. name: Dev-Only - description: >- Admin read API: institution-scoped order, file, reconciliation, SLA, and processing-stats queries, plus audit-trail integrity verification. PII fields are masked unless the caller proves a cleartext grant. name: Admin - description: >- Cross-organization subject summary: consolidates a subject's active blocks across the caller institution's Midaz organizations. Reading a subject by document is a privileged, audited PII access. name: Cross-Org paths: /admin/sta-dlq/{eventId}/acknowledge: post: tags: - STA Dead-Letter summary: Record the human treatment of a parked STA event description: >- Writes the audit record that answers the three-day dead-letter window: which parked record, from which direction, under which parking token, and what the operator did about it (replayed, recorded, escalated). It does NOT remove anything: the dead-letter destination is the Kafka topic lerian.streaming.br-sisbajud.dlq, a LOG with its own retention, so a treated record stays exactly where it is and this acknowledgement — not the record's absence — is what says it was handled. Replaying means seeking the consumer group back to the source offset the record's headers name. Answers with a receipt id for the ticket. 422 when the parking token is not one the consumer emits, when the action is unknown, or when institutionId or eventId are missing — the refusal carries a code and a canned detail, so the valid tokens are published as this request's reason enum rather than named in the answer. operationId: acknowledge-sta-dlq-event parameters: - description: >- Lerian STA's event id, exactly as it appears on the parked message. It is a string on Lerian STA's side and is not required to be a UUID. in: path name: eventId required: true schema: description: >- Lerian STA's event id, exactly as it appears on the parked message. It is a string on Lerian STA's side and is not required to be a UUID. examples: - evt-7f3c9a10 type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/STADLQAcknowledgeRequest' responses: '200': content: application/json: schema: $ref: '#/components/schemas/STADLQAcknowledgeResponse' description: OK '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Internal Server Error default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error components: schemas: STADLQAcknowledgeRequest: additionalProperties: false properties: action: description: >- What you did: replayed (cause fixed, message shovelled back — the consumer is idempotent), recorded (the disposition stands; the commonest case is parse_rejected, where the remittance row is already REJECTED), escalated (the order could not be reproduced inside the window and the institution is talking to the court). enum: - replayed - recorded - escalated examples: - replayed type: string institutionId: description: >- The institution on whose behalf the dead-letter queue was drained. This is NOT necessarily the institution the message resolved to: institution_unresolved is itself one of the parking reasons, and a message parked under it resolved to nobody. In multi-tenant mode it is the tenant whose vhost the queue lives in. examples: - 44444444-4444-4444-4444-444444444444 type: string note: description: >- Why, in your own words. MUST NOT contain personal data (CPF/CNPJ, names, process numbers) or monetary values: it is written verbatim into a permanent, append-only audit record. Text carrying a run of more than 10 digits is refused with 422 — that is a floor against pasting an identifier, not a check that recognises a name. examples: - >- institution config was missing the STA credential; added and replayed type: string queue: description: >- Which of the two queues the message was parked from. These are the values the metric's queue label carries — the direction, not the configured queue name, so the record can be read next to the series. enum: - inbound - outbound examples: - outbound type: string reason: description: >- The parking token, read from the message's x-sisbajud-reason header. The values are the consumer's closed set; "other" is deliberately absent, being the fallback the code produces for a token nobody declared. enum: - direction_mismatch - doctype_header_mismatch - doctype_not_allowed - doctype_pair_mismatch - doctype_unexpected_shape - doctype_unmapped - event_duplicate - handler_not_wired - handler_panic - institution_unresolved - lock_held - object_key_out_of_scope - object_missing - parse_rejected - payload_shape_invalid - payload_too_large - receive_transient - sha256_mismatch - sta_state_unknown - tenant_scope_mismatch - tenant_set_unavailable - terminal_conflict - transfer_not_found - transition_out_of_order examples: - institution_unresolved type: string required: - institutionId - queue - reason - action type: object STADLQAcknowledgeResponse: additionalProperties: false properties: receiptId: description: >- The audit record's id. It identifies THIS acknowledgement, not the message: Lerian STA's event id is a string and is recorded as the audit correlation id. examples: - cccccccc-cccc-cccc-cccc-cccccccccccc type: string required: - receiptId type: object Detail: additionalProperties: true 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 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 ````