session_required

Sign-in required. Answered with 401.

What it means

An endpoint that acts on the console session met no session in force. It answers two situations: no session was presented at all – no bearer, or a bearer that is not a tigby_sess_ token – and a session token that was presented but is unknown, revoked, or expired. Sessions come from a consumed magic link and end on logout or expiry.

What to do

Sign in again through the console. Agents authenticate with an API key, not a session.

The body

{
  "type": "https://tigby.eu/problems/session_required",
  "title": "Sign-in required",
  "status": 401,
  "detail": "…what was refused, naming this request's own values",
  "code": "session_required",
  "doc_url": "https://docs.tigby.eu/errors/session_required",
  "agent_hint": "…the next step, for software"
}

Branch on code. The detail names this request's own Handle, id or limit and is not part of the contract.