List retained messages
Every message the Courier holds because no engine could receive it, every rail, oldest retention first. Read-only, and it never carries the message’s content. A releasable message leaves by itself on the first re-check after its cause lifts — its account enters the ownership map, its owner is enabled again. An UNRECOGNIZED_TYPE of a non-financial code releases once a delivery mode is declared for its code and is not re-checked before that; one of a financial code releases on the re-check after a Courier release reads its destination. Each is re-checked at most once a minute, and within that minute while the tenant holds up to about 6,000 due retentions and its queue is empty, or about 600 while messages keep arriving (re-checks then take at most a tenth of the consumer’s time; measured at 10 ms a re-check); above that, less often in proportion. Re-evaluate one to have it re-checked first: within a second while messages arrive, within 10 seconds otherwise. A Pix retention is re-checked at most once a minute. A re-evaluation has it re-checked within about 10 seconds while the engines answer; Pix tenants are re-checked one after another, and a tenant’s pass that meets an engine that does not answer takes up to about 75 seconds, which every tenant after it waits out. Its release is a delivery the Courier starts with no vendor waiting: the engine’s answer is stored and answers the vendor’s next resend.
Authorizations
JWT bearer token issued by the identity provider.
Query Parameters
Page, 1-based.
x >= 1Items per page.
1 <= x <= 200Filter by rail. Omitted returns every rail.
spb, pix Filter by retention reason.
UNRECOGNIZED_TYPE, ACCOUNT_UNASSIGNED, CLASSIFICATION_FAILED, OWNERSHIP_DECISION_UNAVAILABLE, DELIVERY_FAILED 
