/auth/refreshRefresh an access token
Issues a fresh access token from the secure refresh cookie set at sign-in, and rotates that cookie, keeping the member signed in without asking for the password again.
Access tokens expire. Rather than signing in again, call this endpoint with the
account id and the sid returned at sign-in. The secure refresh cookie set by
POST /auth/login or
POST /auth/login-sso travels with the request and is
what authorises the exchange, which is why no bearer token is needed here.
Replace your stored token with access_token and use
access_token_expires_at to schedule the next refresh. The response also sets a
rotated refresh cookie through Set-Cookie: keep the newest one, because the
cookie you sent has been rotated out. refresh_token_expires_at is the point
past which
refreshing stops working and the member signs in again from the beginning.
Nothing in the body identifies the session on its own. If your client drops
cookies, the call cannot succeed. In cURL, keep a cookie jar from the sign-in
call and send it back. In the browser, set credentials: "include". In Rust,
build the reqwest client with .cookie_store(true).
user_idnumberrequiredsidstringrequired