authentication_required

Authentication required. Answered with 401.

What it means

The endpoint needs a credential and the request presented none Tigby could read – no Authorization header, or a bearer that is not one of Tigby's token shapes. An endpoint that acts on the console session answers session_required in the same situation; every other one answers this.

What to do

Use an Admin Key (tigby_admin_…) for Org-level calls or an Identity Key (tigby_id_…) for one Identity. Admin Keys are created in the console under API keys or with POST /api/keys. Do not retry without a key.

The body

{
  "type": "https://tigby.eu/problems/authentication_required",
  "title": "Authentication required",
  "status": 401,
  "detail": "…what was refused, naming this request's own values",
  "code": "authentication_required",
  "doc_url": "https://docs.tigby.eu/errors/authentication_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.