prasadu507 The best practice here would be to implement retry logic that can detect an expired session key error response from the API, acquire a new fresh session key, and make the API call again.
Trying to track the session key inactivity period may be futile, as you would still need retry logic to account for the "when the community is restarted" scenario.
Additionally, artificially attempting to keep the session active by making a passive request every 30-X minutes may unnecessarily tie up system resources, and again you would still need to account for the other scenarios of expiring after 24 hours or after a restart.
