Get Session State
Retrieve the current state of the session: its status, where your customer is in the experience, and its dates.
A webhook is the recommended way to follow a session — configured once per application in the Console, not per session. This endpoint is for keeping your backend in step when you cannot receive one, or for recovering a session’s state after a lost connection.
Branch on is_closed. While it is false the session is alive — your customer may still connect another bank, or come back to the experience. The HTTP code says the same: 200 once the session is finished, 202 while it is open, with the same body either way.
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
Response
200 OK
The session is FINISHED and nothing about it will change.
The flow this session belongs to: always financial-rider.
The screen the end user is on — or, once the session is over, the last one they reached.
The status of the session. READY while it is open; any other status is final.
The deadline: a session still open at this moment closes as TIMED_OUT. Always present — 12
hours after creation when you did not ask for another.
Whether the session is over. Trust this field — not the arrival of a webhook — to know that nothing about the session will change.
A human-readable note on the status, when there is one.
Delivery status of the financial-rider:ended webhook.