Refresh bearer token

Gives you a new bearer token with a full lifetime, worked out from the
token you send with the request. Use it to keep a long-running
integration signed in without sending your client_secret again.

The token you already hold keeps working until its own expiry time —
nothing is switched off early, so anything already in flight can
finish. Call /api/v4/refresh shortly before the token you hold runs
out. If it has already run out, this call answers 401 and you will
need to sign in again with your client_id and client_secret.

Only a token you got from POST /api/v4/authenticate can be refreshed. Send a Sanctum API key or an OAuth access token instead and you get 403, with no new token. A Sanctum API key does not expire, so there is nothing to refresh. An OAuth access token is renewed by the sign-in that issued it.

If the API client your token was issued to has been removed, you get 401 and no new token, even while the token you hold has time left.

Because this call is a POST, a credential without the api:write scope (a read-only Sanctum API key or user token) gets 403 with insufficient scope: api:write, even though the call changes nothing.

Deprecated. This way of signing in is being replaced. For a new integration, ask LendingWise support for a Sanctum API key for your processing company instead: an API key does not expire, so there is no refresh to run. Tokens issued here still work, and a reply to a call that used one carries the Deprecation, Warning and Link headers described in RFC 8594. No retirement date has been set.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Responses

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json