Preview the direct order purge (dry run)
Lists up to limit (at most 100) direct orders eligible for erasure as of now, in the institutions this executor owns, oldest eligibility first; the same predicate as the purge-eligible gauge, the money rule and the parent rule of the erase. A permanent block’s permanentUntil lives only in its sealed body, so the erase may still refuse a listed permanent order (SBJ-0057). The preview is a dry run only: nothing is erased, and each erase is a separate POST …/orders//erase. A human platform-administrator action (direct_order_erasure:purge_preview): 403 SBJ-0044/SBJ-0045 for M2M or tenant-carrying tokens. 422 SBJ-0058: dryRun not true, limit out of range, reason or ticket invalid. 422 SBJ-0059: multi-tenant deployment.
Autorizaciones
JWT bearer token issued by the identity provider.
Cuerpo
Must be true: the preview only lists the eligible orders; each erase is a separate request.
true
Most orders listed, 1 to 100; 0 or absent lists up to 100.
100
Required: retention-purge or lgpd-subject-request.
"retention-purge"
Required: the request id (at most 64 characters, no personal data).
"PURGE-2026-10"
Respuesta
OK
Instant the eligibility was read (UTC).
Always true: nothing was erased.
Direct orders eligible for erasure as of asOf, oldest eligibility first.
True when the listing stopped at its read bound before it found limit orders or ran out of candidates: more eligible orders may exist. Each listed order is one the erase would accept (eligibility and the money rule).

