Get Session Settings | INFONITE

Retrieve the resolved configuration settings applied to the flow session.

This endpoint returns the final settings active for the session. These settings are resolved by merging:

The custom parameters requested in the session initialization payload (Create Session).
The default settings configured for the client application.
Global system defaults.

Its primary utility is diagnostic, allowing clients and auditing tools to verify the exact rules, features, and sandbox configurations executing for the flow session.

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

X-APP-SECRETstring

Application Secret

Path parameters

session_idstringRequiredformat: "object-id"

Session ID to fetch

Response

200 OK
The settings the session runs with

sandboxboolean

Indicates if the session is running in sandbox/mock mode for testing.

consent_levelenum

The level of consent screening displayed to the user inside the widget.

Allowed values:

hooks_extra_datamap from strings to strings

Extra data to be included in the hooks. This data will be returned in the webhook as part of the URL as query parameters. This can be useful to include dynamic data in the webhook. There are some template variables that can be used:

{app_id}: Your app ID
{customer_id}: The customer ID
{session_id}: The Session ID
{parameters_id}: The unique credentials ID, this identifier is computed by the engine based on the fixed part of the credentials (e.g. the username)
{producer}: The producer of the event
{event}: The event that triggered the hook
{status_code}: The status of the flow at the moment of the event For example, passing:

{
  "custom_param": "customValue",
  "current_event": "{event}",
  "status": "{status_code}",
  "id": "{session_id}"
}

Will result in the following URL: https://your.url.com/your/path?custom_param=customValue&current_event=ended&status=COMPLETED&id=67d7d9b72eb0693e7da47a0e

Note: This data is not encrypted and should not contain sensitive information.

executions_featureslist of objects

The list of public administration portals and features configured for extraction.

completion_modeenum

The redirection behavior mode executed after the user completes the flow.

Allowed values:

completion_extra_datamap from strings to strings

Extra data to be included in the redirect URL. This data will be added to the the url as query parameters. This can be useful to include dynamic data in the webhook. There are some template variables that can be used in the URL:

{app_id}: Your app ID
{customer_id}: The customer ID
{session_id}: The Session ID
{status_code}: The final status code of the session For example, passing:

{
  "custom_param": "customValue",
  "status": "{status_code}",
  "id": "{session_id}"
}

Will result in the following URL: https://your.url.com/your/path?custom_param=customValue&status=COMPLETED&id=67d7d9b72eb0693e7da47a0e

Note: This data is not encrypted and should not contain sensitive information.

allowed_engineslist of strings

The engines the session offers right now, computed on every read. Never sent: the administrations a session may use are set with allowed_sources.

allowed_sourceslist of enums

The administrations this session may connect to, in order of preference: what the session was opened with, else your application’s default, else ["tgss", "aeat", "citizen_folder"].

Allowed values:

completion_urlstringOptional

The redirection target URL where the user is sent upon session completion or failure.

Errors

404

Not Found Error

422

Unprocessable Entity Error

429

Too Many Requests Error