List the rounds waiting on a person
The rounds standing on the consent surface, newest first. It is the recovery road for a client that was not attached when refinement-proposed went out — a round proposed by last night’s scheduled fire is answered the next morning, and an announcement nobody heard must not be the only way to find it.
A round is NEVER expired by the boot-recovery pass, unlike a permission or a question: nothing is blocked behind it, so a host restarting leaves it exactly where it was.
Autorizações
Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation.
Parâmetros de consulta
Which rounds to list. pending is the default and the one a client draws an affordance from; answered is the audit of rounds already decided.
pending, answered Opaque pagination cursor from a previous page's nextCursor or prevCursor.
1024Maximum items per page.
1 <= x <= 100
