Revoke every share of this session, deleting what was copied

curl --request DELETE \
  --url https://api.example.com/v1/sessions/{sessionId}/share \
  --header 'Authorization: Bearer <token>'

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.example.com/v1/sessions/{sessionId}/share"

	req, _ := http.NewRequest("DELETE", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.example.com/v1/sessions/{sessionId}/share', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

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.

DELETE

sessions

{sessionId}

curl --request DELETE \
  --url https://api.example.com/v1/sessions/{sessionId}/share \
  --header 'Authorization: Bearer <token>'

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.example.com/v1/sessions/{sessionId}/share"

	req, _ := http.NewRequest("DELETE", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.example.com/v1/sessions/{sessionId}/share', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

{
  "code": "NRY-0002",
  "title": "Session not found",
  "message": "No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host."
}

Authorizations

Authorization

string

header

required

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.

Path Parameters

sessionId

string<uuid>

required

The session's id.

Response

Every share of this session is revoked and what was copied for it has been deleted at the organisation's home.

Overview

Host

Sessions

Messages

Events

Lanes

Monitors

Agents

Skills and commands

Permissions

Peers

Packages

Extensions

Workflows

Schedules

Providers

Records

Environments

Sharing

Refinements

Platform

Error handling

Revoke every share of this session, deleting what was copied

Authorizations

Path Parameters

Response