Solution skill
Rossum tokens expire after ~162 hours - build re-login, dont cache forever
Complete solution
Shows how to fix rossum tokens expire after ~162 hours - build re-login, dont cache forever. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Build a re-login on 401, or set maxtokenlifetimes up front to a value that fits your job schedule. Tokens live about 162 hours by default (settable via maxtokenlifetimes), and you pass the key back in the Authorization header using the Bearer or Token scheme.
Steps
- Rossum tokens expire - about 162 hours by default - so do not cache one forever and wonder why calls start 401ing. Build a re-login on 401, or set maxtokenlifetime_s up front to a value that fits your job schedule. Also note the login response tells you your domain; Rossum is multi-tenant, so point subsequent calls at the domain you got back, not a hardcoded one.
When to use
You are seeing this: Rossum tokens expire - about 162 hours by default - so do not cache one forever and wonder why calls start 401ing. Use this skill when you run into "Rossum tokens expire after ~162 hours - build re-login, dont cache forever".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Edge cases
- Also note the login response tells you your domain; Rossum is multi-tenant, so point subsequent calls at the domain you got back, not a hardcoded one.
Evidence
Source: Rossum reference docs: authenticate with POST /v1/auth/login using username and password; the response carries the key and your domain. Tokens live about 162 hours by default (settable via maxtokenlifetime_s), and you pass the key back in the Authorization header using the Bearer or Token scheme.
Verified resolution: Rossum tokens expire - about 162 hours by default - so do not cache one forever and wonder why calls start 401ing. Build a re-login on 401, or set maxtokenlifetime_s up front to a value that fits your job schedule. Also note the login response tells you your domain; Rossum is multi-tenant, so point subsequent calls at the domain you got back, not a hardcoded one.
Source URL: https://github.com/rossumai/claude-marketplace/blob/HEAD/plugins/rossum-sa/skills/rossum-reference/reference.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_EfHvUJblmjnyIcFlpwWOuw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Rossum tokens expire after ~162 hours - build re-login, dont cache forever <span>— Vectle</span></a>