> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Read a shared session's copied entries > The conversation itself, as this home holds it: the redacted entries that crossed, in the order they were said. ALREADY REDACTED, AND THE ORIGINAL NEVER EXISTED HERE. Every rule ran at the home the entries were published from, which is the only place a *before* exists. Nothing at this end can widen what was sent, and nothing at this end is asked to. THE SAME AUDIENCE RULE THE LISTING APPLIES, and a share this caller may not read answers 404 NRY-0015 rather than 403 — the same answer a share id this home has never seen gets, so the two cannot be compared to learn that somebody's conversation is here. A revoked share and one whose expiry has passed answer identically, for the same reason. EVERY SERVED READ IS RECORDED, unless the reader is the person who published it. The disclosure entry is written before a byte is served and a read whose record cannot be written is not served at all, which is what makes "who opened this" a trustworthy answer rather than a best-effort one. Cursor pagination, oldest first, on the publishing home's own numbering — a conversation is read forwards. ## OpenAPI ````yaml /es/openapi/v3-current/narya.yaml get /v1/shares/{shareId}/entries openapi: 3.1.0 info: title: Narya Host API version: 1.0.0 description: >- The contract between the Narya host and every client. One long-lived host serves this API over a Unix socket in your Narya home. The terminal client and the one-shot command that Lerian ships drive this API, and a client you write drives the same one. Requests authenticate with a bearer token issued by the identity provider the host is configured with. An operation that declares another security scheme also accepts that credential. A request without a valid credential gets 401 with NRY-0011. A caller whose role lacks the permission an operation needs gets 403 with NRY-0028. Submitting a message returns 202 with a turn id. Everything the turn produces streams over GET /v1/events as server-sent events with a typed envelope, and a stream resumes from a Last-Event-ID header. One error envelope: code, title and message. Codes are NRY- followed by four digits. Cursors are opaque. servers: [] security: - bearerAuth: [] tags: - name: host description: The host process itself — version, uptime, mode, store. - name: sessions description: Durable conversation containers. Archive, never destroy. - name: messages description: Submitting work into a session and interrupting it. - name: events description: The server-sent event stream every client consumes. - name: lanes description: Parallel tracks inside a session — main, subagent, side. - name: agents description: Named recipes — instructions, tools, model, policy. Read-only in v1. - name: ladder description: >- What a person can type: the skills and command files in force for one repository, and expanding one into text. Five origins merged, nearest winning a name, the repository's own rungs gated on trust. - name: permissions description: Pending permission asks, decisions, and the decision audit. - name: intercom description: Sessions on one machine finding and messaging each other. - name: packages description: The one thing a user installs — resources, Go code, or both. - name: extensions description: >- Host-side extensions and the operations each exposes over the wire. This is the generic lane a host extension uses to serve its own client half (a TUI component, a web panel) or any API-only consumer, without adding routes to this contract. - name: workflows description: Deterministic multi-agent orchestration runs. - name: providers description: Model suppliers, their auth state, and the model catalogue. - name: monitors description: >- Long-running watchers a session keeps beside its conversation — a test runner in watch mode, a build, a log being followed. Started by the model or by the person, always listed, always killable. - name: records description: The queryable local record of everything that happened. - name: environments description: >- Where a session's code lives and its commands run — this machine, or a container narya operates. A session that names none runs here. - name: schedules description: >- Work the host's own clock starts with nobody present — a repository, a prompt, a rule and what one fire may spend. Cancel, never destroy. - name: sharing description: >- Publishing a session from a developer's own home to the organisation's, and what is held back before a byte leaves the machine. - name: refinements description: >- What this owner has taught narya and allowed it to keep — distilled facts, and the skills, agents and commands the model wrote for itself. Propose, read, consent, roll back. Nothing here fires until a person answers. - name: platform description: >- Calls Lerian's control plane made to a home it hosts, as this home recorded them. paths: /v1/shares/{shareId}/entries: parameters: - $ref: '#/components/parameters/ShareIdParam' get: tags: - sharing summary: Read a shared session's copied entries description: >- The conversation itself, as this home holds it: the redacted entries that crossed, in the order they were said. ALREADY REDACTED, AND THE ORIGINAL NEVER EXISTED HERE. Every rule ran at the home the entries were published from, which is the only place a *before* exists. Nothing at this end can widen what was sent, and nothing at this end is asked to. THE SAME AUDIENCE RULE THE LISTING APPLIES, and a share this caller may not read answers 404 NRY-0015 rather than 403 — the same answer a share id this home has never seen gets, so the two cannot be compared to learn that somebody's conversation is here. A revoked share and one whose expiry has passed answer identically, for the same reason. EVERY SERVED READ IS RECORDED, unless the reader is the person who published it. The disclosure entry is written before a byte is served and a read whose record cannot be written is not served at all, which is what makes "who opened this" a trustworthy answer rather than a best-effort one. Cursor pagination, oldest first, on the publishing home's own numbering — a conversation is read forwards. operationId: listShareEntries parameters: - $ref: '#/components/parameters/CursorParam' - $ref: '#/components/parameters/LimitParam' responses: '200': description: One page of this share's conversation, oldest first. content: application/json: schema: $ref: '#/components/schemas/ShareEntryPage' '400': $ref: '#/components/responses/BadRequest' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' components: parameters: ShareIdParam: name: shareId in: path required: true description: >- The share's id, as `SessionShare.shareId` reports it: 26 characters of RFC 4648 base32 drawn from a cryptographic source, carrying no encoding of anything. It is NOT a uuid and is deliberately unrelated to the session id it was published from — a share id travels, so an id derived from a session would make every leaked link a statement about the machine it came from. schema: type: string minLength: 26 maxLength: 26 pattern: ^[A-Z2-7]{26}$ CursorParam: name: cursor in: query required: false description: >- Opaque pagination cursor from a previous page's nextCursor or prevCursor. schema: type: string maxLength: 1024 LimitParam: name: limit in: query required: false description: Maximum items per page. schema: type: integer minimum: 1 maximum: 100 default: 25 schemas: ShareEntryPage: type: object description: >- One page of a shared session's copied entries, oldest first. THE ROWS ARE ShareDeliveryEntry, which is the shape they CROSSED in rather than a second vocabulary for the same four facts. What is held here is exactly what was delivered — already redacted, still in its place — so a reading of it that differed from the delivery's would be this home describing somebody's conversation in words nobody sent. required: - items - limit properties: items: type: array items: $ref: '#/components/schemas/ShareDeliveryEntry' nextCursor: type: string description: >- Pass as `cursor` for the next page. Absent at the end of the conversation as this home holds it — which, for a `sync` share still being carried, is where the next delivery continues from. limit: type: integer minimum: 1 description: The page size this host applied. ShareDeliveryEntry: type: object description: >- One entry as it crosses: already redacted, still in its place. It is the same four facts SessionSharePreviewEntry reports, because it is the same computation — what a person was shown before the bytes left is what the bytes are. required: - id - kind - sequence properties: id: type: string format: uuid description: >- The entry's own id at the home it was published from. It is what makes a delivery idempotent: the receiving home recognises a retry by it, which is the one thing the sending home cannot do for itself when an answer is lost. kind: type: string enum: - user-message - assistant-message - tool-call - tool-result - summary - system - intercom - monitor-event description: The transcript row's kind, unchanged by redaction. sequence: type: integer format: int64 minimum: 1 description: >- The entry's place in the transcript at the publishing home. Carried rather than re-derived: entries arrive in batches a drain decided the shape of, so arrival order is the drain's history and not the conversation's. text: type: string description: >- What is being sent for this entry, with every rule already applied. Absent for an entry that carries nothing this surface publishes — such an entry still crosses, so the sequence a reader follows stays honest. Error: type: object description: >- The single error envelope every operation returns. Codes are NRY- followed by four digits and are catalogued in the top-level x-error-catalog extension. required: - code - title - message properties: code: type: string pattern: ^NRY-[0-9]{4}$ description: Machine-readable error code from the NRY catalogue. title: type: string maxLength: 256 description: Short human-readable summary of the error class. message: type: string maxLength: 4096 description: Specific, actionable description of what went wrong. fields: type: object description: Per-field validation problems. additionalProperties: type: string examples: - code: NRY-0002 title: Session not found message: >- No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host. responses: BadRequest: description: Malformed request — invalid parameter, cursor, or JSON body. content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: The addressed resource does not exist on this host. content: application/json: schema: $ref: '#/components/schemas/Error' InternalServerError: description: The host failed — including a store that refuses writes (NRY-0012). content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- 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. ````