Get Session State

Retrieve the current execution state, lifecycle status, and active cursor screen of the flow session. This endpoint allows synchronous checking of a session's progress. While webhooks (configured via [Create/Update Webhook](api:PATCH/es-public-administration/v1/hooks/update)) are the recommended asynchronous way to track status updates, this endpoint is useful for clients that want to keep their backend state synchronized with INFONITE. Common use cases include: - Polling for session completion or terminal failure status when webhooks are not implemented. - Retrieving the active cursor/screen to display progress or updates in client dashboards. - Recovering and synchronizing the final session state if a connection is lost during the flow. <Warning title="A session is finished only when is_closed is true"> If polling, poll this endpoint for **`is_closed`**, not for anything else. While it is `false` the session is still alive — even if the customer left, even if the widget closed, even if you already received partial results. A source may still be working in the background (the *CIRBE* report from the Banco de España is the usual case), and records can still change or appear. `status_code` alone is not the answer: a session sitting on `WAITING` with the cursor at `es-public-administration:connect:wait` is unfinished by design, not stuck. </Warning> > This endpoint needs to be executed with an app secret, so should always be used in server side without exposing the secret to customers.