I replied to @JokerMartini in another similar thread, with an implementation that slightly resembles @michael.delaporte’s answer above: SSLError: wrong version number - #13 by danielskovli
Main difference being that I decided to use an instance pool and a pool manager to handle (and grow) the connections, instead of binding them directly to a thread-id. Reason for this being that two different threads can successfully share a connection instance, as long as they don’t concurrently call the API.