Check a token
Check whether a token can still be used, and what it is scoped to.
Worth calling before a batch run, and worth calling when a tokenized execution is refused: this is where the reason lives.
status_code, and what each one means for you
context repeats the scope: engine_reference, customer_id, locking_hash and the features the token may request, and source_execution_id, the execution whose credentials it holds now. date_expiration is the hard end of its life — 90 days from the last exchange, not extended by use — after which the stored credentials are deleted. Renewing the connection before then sets a new one.
The token key is never returned here. If you lost it, the token is unusable until your customer connects the account again, which renews it with a new key.
This endpoint needs to be executed with an app secret, so should always be used in server side without exposing the secret to customers.
Authentication
Path parameters
The stored-credentials token, as the exchange returned it.
Response
200 OK
What the token is for — the engine, the customer and the features it was scoped to — and whether it still works. It never carries the credentials, nor your key: nothing here can be turned back into a password.
Identifies the stored credentials — the same id you send when you run an execution with them.
When it stops working. Decided at the exchange and not extended by use: a token that runs
every month still expires on this date. Connecting the same account again renews the token
— the same token_id — and sets a new date.
Why it is in that state, in our words. Prose: read it, do not parse it.