Client (Lära and Via HTML)

Created by Miro Lagueux, Modified on Mon, 31 Aug at 9:09 AM by Miro Lagueux

TABLE OF CONTENTS
Client/test

Client

The "client" represents your organization on the SVIeSolutions server. They are named "client" in the API.

Retrieves a confirmation of communication with the portal API.
API call address : https://.../lmsapi/client/test

Example of request call content for a confirmation of communication with the portal API (submit empty braces):

{}

Name	Required	Comments/description
		No field is required.

Example of the response call content for a request for a confirmation of communication with the portal API:

{
    "success": true
}

Name	Required	Comments/description
success		Indicates a positive response from the API.

Name	Host	Duration	Description
_fw_crm_v	sviesolutions.freshdesk.com	1 year	Freshchat/Freshworks cookie (Used to track Visitor/User identity and chat sessions performed by the User).
_x_w	sviesolutions.freshdesk.com	Session	Contains the shard ID at which the account runs on.
_x_m	sviesolutions.freshdesk.com	Session	Contains the state of the shard.
_helpkit_session	sviesolutions.freshdesk.com	Session	Your secret key for verifying cookie session data integrity. If you change this key, all old sessions will become invalid!
helpdesk_node_session	sviesolutions.freshdesk.com	Session	An encrypted hash that stores the secret key and id of the login attempt.
user_credentials	sviesolutions.freshdesk.com	2 months	Used for user authentication.
wf_order	sviesolutions.freshdesk.com	Session	Used to check in which the order the tickets are filtered for custom ticket filters eg: due_by, agent_responded_at, requester_responded_at, etc.
wf_order_type	sviesolutions.freshdesk.com	Session	Used to check if the order is ascending or descending for custom ticket filters.
wf_filter	sviesolutions.freshdesk.com	Session	Denotes which filter is applied for the tickets list.