Once the session with the public API comes to an end, in order to avoid unneeded system load, it's a good practice to terminate the authenticated session calling this API This allow KAPTO to free the user session and the user related cached configuration. Thi sis particularly important because KAPTO could be configured to limit the number of concurrent session of the same user or the overall users along a certain organization.