The live shares of this session, and who each one is for

What this session has been published as, from the publishing end: one row per share that is still live, carrying who it is for. IT IS THE WAY IN TO CHANGING THAT AUDIENCE. A share is retargeted by its id (PUT /v1/shares/{shareId}/recipients) and a person has a conversation rather than a 26-character id, so this is where a client learns which shares exist and what each one currently names. A client holds no share id of its own between runs and derives nothing. REVOKED AND EXPIRED SHARES ARE NOT HERE. Their entries have been deleted and their audience can never change again, so a row for one would be an offer to retarget a conversation that no longer exists. WHO MAY READ IT is narrower than who may read the session: whoever opened the session, or a member carrying members:manage. A colleague who may read the conversation may not read the list of the colleagues it was addressed to — that list is a statement about people rather than about the work, which is the line the disclosure audit beside it already holds and the reason a recipient’s own read of a copy never reports who else was named. A caller who may not is answered 403 NRY-0028. A SHARE THIS CALLER MAY NOT CHANGE IS NOT HERE EITHER, so no row is ever offered that PUT /v1/shares/{shareId}/recipients would refuse. The rows are the shares this caller may settle: their own, and every one of them for a member carrying members:manage. A session somebody ELSE published — which an unmarked session allows, since it is the organisation’s already — therefore lists nothing for the person whose session it is, rather than a row naming the colleagues another member addressed their work to. An empty list is “nothing here for you to change” and not “this was never published”.

GET /v1/sessions/{sessionId}/share

The live shares of this session, and who each one is for

cURL

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

200

{
  "shares": [
    {
      "shareId": "K7QX2ZM4YB6PWNRJ5TFHCDA3EV",
      "sessionId": "6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d",
      "mode": "sync",
      "state": "active",
      "createdAt": "2026-09-08T09:15:00.000Z",
      "expiresAt": "2026-10-08T09:15:00.000Z",
      "recipients": [
        "user_grace"
      ]
    }
  ]
}

Autorizaciones

Authorization · string · header · requerido

Enforced on every transport, with no exempt operation. A person's request 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 — except a request with no token on a laptop's socket from the OS user the kernel names as the host's own, which is that machine's user.

Parámetros de ruta

sessionId · string<uuid> · requerido

The session's id.

Respuesta

200

application/json

The live shares of this session, newest first.

The live shares of one session, newest first. NO CURSOR AND NO LIMIT. A session is published once, occasionally twice, and every row is one a person may act on — so paging here would be a mechanism guarding a list that is already short.

shares · object[] · requerido

Show child attributes