not_found

​

The shape

{
  "error": {
    "type": "not_found",
    "code": "not_found",
    "message": "No session sess_0aaaa is visible to this account.",
    "doc_url": "https://docs.fiveninelabs.com/errors/not_found",
    "request_id": "req_6bb90x"
  }
}

​

How to fix

• Check the id’s prefix against the resource: sess_ for sessions, ext_ for extractions, mon_ for monitors, whep_ for webhook endpoints. A sess_ id on /v1/webhooks/{id} is a 404, not a type error. (The extractions and monitors surfaces answer 501 on every id, right prefix or wrong — they aren’t served yet.)
• Confirm you’re calling with a key from the same account that created the resource — keys on other accounts see nothing, by design. fn_test_ and fn_live_ keys share the account, so that split is not the cause.
• List what the account can actually see: GET /v1/sessions (covers extractions and monitor runs via type).
• Redaction is planned, not served — DELETE /v1/sessions/{id} answers 501 today, so nothing you can call yet produces a redacted run. When it ships, a redacted run will keep its ledger skeleton while its data reads 404; if you rely on long-lived reads, note runs are retained at least 90 days.

​

Reproduce it

curl https://api.fiveninelabs.com/v1/sessions/sess_0doesnotexist \
  -H "Authorization: Bearer $FIVENINE_TEST_KEY"