Validate bearer token

post deprecated

https://api.lendingwise.com/api/v4/validate

Checks whether the bearer token you send is still valid, and tells you
how many seconds it has left.

This is a cheap call, so it is worth making before you start a long
batch of work: it lets you decide whether to get a fresh token first.
While the token is still good you get 200 with success and
expires. Once it has run out you get 401.

This call only reads. It never replaces or extends the token — use
/api/v4/refresh for that.

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

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

Language

Credentials

Bearer

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Whether the token is still good, and how many seconds it has left.

400Your request body could not be read, so nothing was changed. error.details.reason says what the problem was.

401Your bearer token is missing, or it is not valid. Get a new one from POST /api/v4/authenticate and send it again.

415Your body is JSON, but it was not labelled as JSON, so it was not read and nothing was changed. Send it again with Content-Type: application/json.

429You have made too many calls, so this one was refused and nothing was changed. Retry-After says how many seconds to wait; sending the same request again after that works.

defaultAny other failure. The shape is the same as every other error reply, so the same code can read it.