List sessions that touched a file
Answers “which sessions touched this file”, over the same three session kinds searchRecords covers: the caller’s own, the ones marked for the organisation, and every session when the caller holds the read-private permission. A share adds none here either: what a share delivers is transcript entries, and a file listing reports the file changes, which a share does not carry at all. An unknown path, and a path touched only by sessions outside those three kinds, both return an empty page rather than an error.
Authorizations
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.
Query Parameters
The file path to look up.
4096Restrict the answer to the conversations the caller owns. It names nobody and takes no name: the subject comes from the verified token and from nowhere else, which is what keeps it from being the owner parameter this contract deliberately does not have — an owner a caller can name is an owner anybody can be. It is not a permission and can only ever narrow. Combines with every other filter here.
Opaque pagination cursor from a previous page's nextCursor or prevCursor.
1024Maximum items per page.
1 <= x <= 100
