> ## 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. # Revoke every share of this session, deleting what was copied > Stops sharing this session and DELETES what was copied to the organisation's home. Not a flag that hides it there, and not a client that stops drawing it: the copied entries are removed from the organisation's store. IT ANSWERS AFTER THE DELETION HAS HAPPENED, not after accepting a request to perform one. A revocation that is queued is a revocation that has not occurred yet, and the person asking for one is usually in a hurry. So 204 means the data is gone; 503 NRY-0029 means the organisation's home did not answer, this machine has stopped sending anything more for the share, and the copy is still there until the request is repeated. THE SHARE RECORD SURVIVES AS A TOMBSTONE, and only the record: it carries the disclosure history, which is the one thing that has to outlive the data it describes. It also makes the revocation win against work queued before it — entries offered for a tombstoned share are refused 410 NRY-0031 forever, so a developer who was offline for a week cannot replay a conversation into a share somebody revoked on Tuesday. EVERY SHARE OF THE SESSION STOPS. Publishing twice creates two shares, and a person revoking a conversation means the conversation. RE-SHARING AFTERWARDS IS A NEW SHARE ID. A revoked id is never reused, because an id that came back to life would make the audit ambiguous about which disclosure it is recording. Revoking twice is not an error, and neither is revoking a session nobody published: the state asked for is the state it is in. The instant recorded stays that of the first revocation. ## OpenAPI ````yaml /pt/openapi/v3-current/narya.yaml delete /v1/sessions/{sessionId}/share 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/sessions/{sessionId}/share: parameters: - $ref: '#/components/parameters/SessionIdParam' delete: tags: - sharing summary: Revoke every share of this session, deleting what was copied description: >- Stops sharing this session and DELETES what was copied to the organisation's home. Not a flag that hides it there, and not a client that stops drawing it: the copied entries are removed from the organisation's store. IT ANSWERS AFTER THE DELETION HAS HAPPENED, not after accepting a request to perform one. A revocation that is queued is a revocation that has not occurred yet, and the person asking for one is usually in a hurry. So 204 means the data is gone; 503 NRY-0029 means the organisation's home did not answer, this machine has stopped sending anything more for the share, and the copy is still there until the request is repeated. THE SHARE RECORD SURVIVES AS A TOMBSTONE, and only the record: it carries the disclosure history, which is the one thing that has to outlive the data it describes. It also makes the revocation win against work queued before it — entries offered for a tombstoned share are refused 410 NRY-0031 forever, so a developer who was offline for a week cannot replay a conversation into a share somebody revoked on Tuesday. EVERY SHARE OF THE SESSION STOPS. Publishing twice creates two shares, and a person revoking a conversation means the conversation. RE-SHARING AFTERWARDS IS A NEW SHARE ID. A revoked id is never reused, because an id that came back to life would make the audit ambiguous about which disclosure it is recording. Revoking twice is not an error, and neither is revoking a session nobody published: the state asked for is the state it is in. The instant recorded stays that of the first revocation. operationId: revokeSession responses: '204': description: >- Every share of this session is revoked and what was copied for it has been deleted at the organisation's home. '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' '503': description: >- The organisation's home did not answer (NRY-0029), so its copy of this session has NOT been deleted. This machine has stopped sending anything further for the share; repeating the request once the home answers completes the deletion. content: application/json: schema: $ref: '#/components/schemas/Error' components: parameters: SessionIdParam: name: sessionId in: path required: true description: The session's id. schema: type: string format: uuid responses: Forbidden: description: >- The caller is authenticated and is not allowed this operation (NRY-0028 or NRY-0030). 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' schemas: 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. 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. ````