Session

These endpoints handle clerk session operations like start/stop session, keep-alive, ...etc.

In Q-net Pro 7, the clerk login doesn't start a clerk session, instead generates an authentication token to access to endpoints. To start a clerk session, you should call the start session endpoint. To stop the session (e.g. end of the worktime), you should call the stop session endpoint.

📄️Start session

This endpoint starts a new clerk session. The endpoint has no response if it was successful.

📄️Check session

This endpoint checks the current clerk session. If there is a live session, it returns with the counter ID and status ID if the clerk is in any clerk status.

📄️Keep alive

If there is no REST communication from the counter to server for a long time, the server will stop the clerk session. To avoid it, you should call the keepAlive endpoint once per minute.

📄️Idle times

For clerk statistics, the counter should send the measured idle times to the server. It can be sent everytime during the clerk session. It's recommended to send when the counter calls a ticket or stop the session.

📄️Before stop session

You can check if there are any waiting tickets, redirected tickets or tickets on waitlist for the clerk. This endpoint returns these values and you can show a confirmation dialog on the counter before stopping the session.

📄️Stop session

This endpoint stops the clerk session. The endpoint has no response if it was successful.