I use Python a lot for Genesys Cloud API calls, especially for reports, data extraction, operational analysis, and automation scripts.
In my case, I do not usually recommend starting with the SDK by default for these scenarios. Back in 2024, I was evaluating whether the best approach would be to use the official SDK or build my own lightweight API wrapper/class.
During some tests and executions, I noticed an initial delay of around 10 seconds when running scripts with the SDK. After moving to my own internal library, focused only on the endpoints and authentication patterns I actually needed, the performance improvement was significant.
For me, the main benefits of a custom Python library were faster startup, simpler code, more control over retries and errors, easier logging, and better alignment with the way I build reports and automations.
That said, I still see value in the SDK for teams that prefer generated models, standardized methods, and broader API coverage. But for high-volume reports, batch processing, and controlled automation jobs, I personally prefer a lean Python wrapper around the Genesys Cloud Platform API.
------------------------------
Matheus Mendonca
------------------------------