Since only one API is used in the CS object we can make use of connection pooling integrated in requests.Session, this would save the https negociation between requests
Havin a session per object could allow us to configure it in the future (adding specific headers/timeouts/etc.)
Use case: on jaas.ai we would like to have a persistant session to be able to make requests analysis (duration, etc.).
Summary