Resolve a parked DIRECT permanent attempt

The audited resolution of a PARKED DIRECT permanent block attempt (its reactive write failed every retry, or its window passed, so its block account holds every new credit) of a single-tenant deployment (multi-tenant: 422 SBJ-0053). Declaring no effect releases the account: credits resume and the open-order probe lets the order go; the attempt stays FAILED. Acknowledging the effect journals movedAmount as the write’s landed effect: it is added to the permanent’s accumulated amount (the next credit blocks only the remainder; reaching the target closes the block) and the attempt becomes BLOCKED with its result. On a permanent already CLOSED the attempt is SKIPPED_CLOSED, nothing reopens, and closed_with_effect is alarmed. A human platform-administrator action (executor_human_decision:resolve): an application token (SBJ-0044) or a tenant-carrying token (SBJ-0045) is refused with 403. The journal rows, the attempt and the audit row commit in one transaction. 200 outcome NOOP: the same resolution was already journaled. 404: unknown attempt, or one of an institution this executor does not own. 409 SBJ-0061: not parked, or the order is busy. 409 SBJ-0054: the journal shows money moved. 409 SBJ-0055: already resolved as no effect. 422 SBJ-0052: invalid request (the reason is named in the answer, e.g. LEG_ALLOCATION_REQUIRED). 422 SBJ-0062: movedAmount above the cap.

POST /v1/admin/executor/orders/{orderId}/permanent-attempts/{attemptId}/resolution

Resolve a parked DIRECT permanent attempt

cURL

curl --request POST \
  --url https://api.example.com/v1/admin/executor/orders/{orderId}/permanent-attempts/{attemptId}/resolution \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "allocation": [
    {
      "accountId": "0193b2c4-acc1",
      "amount": "10.00"
    }
  ],
  "ledgerEvidence": {
    "kind": "transaction",
    "observedAt": "2026-10-29T11:30:00Z",
    "reference": "midaz-tx-3f9a1c7e"
  },
  "movedAmount": "30.00",
  "reason": "OPS-4512: ledger statement reviewed.",
  "resolution": "effect-acknowledged"
}
'

200

{
  "attemptId": "<string>",
  "orderId": "<string>",
  "outcome": "RESOLVED",
  "resolution": "<string>",
  "resolvedAt": "2023-11-07T05:31:56Z",
  "resolvedBy": "<string>"
}

Autorizaciones

Authorization · string · header · requerido

JWT bearer token issued by the identity provider.

Parámetros de ruta

orderId · string · requerido

The executor order's identifier (UUID).

Ejemplo:

"0b9b7c2e-4f8a-4d3e-9a51-7c2d1e0f3a44"

attemptId · string · requerido

The parked permanent attempt's identifier (UUID).

Ejemplo:

"1d2e3f40-5a6b-4c7d-8e9f-0a1b2c3d4e5f"

Cuerpo

application/json

allocation · object[] | null

Optional per-leg allocation of movedAmount: required when a partial amount of a write of several origin legs is acknowledged (422 SBJ-0052, LEG_ALLOCATION_REQUIRED); it must name the write's own legs once each, each at most its amount, summing to movedAmount (LEG_ALLOCATION_INVALID).

Show child attributes

ledgerEvidence · object

Required: a parked write is uncertain by definition. Its kind is transaction on effect-acknowledged (the reference is journaled as the ledger transaction). observedAt must not be before the attempt's write. Stored only in the sealed audit row.

Show child attributes

movedAmount · string

Required with effect-acknowledged, refused otherwise: the decimal amount above zero the write moved. At most the permanent's remaining while it is open, at most the write's journaled amount always (422 SBJ-0062). Never echoed, logged nor audited.

Ejemplo:

"30.00"

reason · string

Required. Short justification or ticket (at most 200 characters, no personal data). Never echoed.

Ejemplo:

"OPS-4512: ledger statement reviewed."

resolution · string

Required. proven-no-effect: the ledger shows the parked write never landed; the account is released and new credits resume (the attempt stays FAILED). effect-acknowledged: the write landed movedAmount; it counts toward the permanent block and the attempt becomes BLOCKED.

Ejemplo:

"effect-acknowledged"

Respuesta

200

application/json

OK

attemptId · string · requerido

The permanent attempt's identifier.

orderId · string · requerido

The executor order's identifier.

outcome · enum<string> · requerido

RESOLVED: journaled now. NOOP: the same resolution was already journaled; nothing changed.

Opciones disponibles: RESOLVED, NOOP

resolution · string · requerido

The resolution journaled, as requested.

resolvedAt · string<date-time> · requerido

Instant of the request (UTC).

resolvedBy · string · requerido

Subject of the platform administrator who made the request.