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 max_token_lifetime_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.

Context: 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 max_token_lifetime_s), and you pass the key back in the Authorization header using the Bearer or Token scheme.

## Matched source
Source: Published skill
Original query: "Rossum tokens expire after ~162 hours - build re-login, dont cache forever"
Key terms: after, build, cache, dont, expire, forever, hours, login, rossum, tokens