Starting with 8.0U3, a single session allows users to execute SOAP as well as REST APIs. With these changes, session management is consolidated and would be done entirely within VPXD.
vCenter Server 8.0U3 or above
Following limits are applicable only to releases earlier than 8.0 U3. Starting with 8.0U3, a single session allows users to execute SOAP as well as REST APIs. With these changes, session management is consolidated and would be done entirely within VPXD.
Unified Management and Automation API Sessions: Starting with vCenter 8.0 Update 3, you can combine vSphere Management API (VIM) and vSphere Automation API (vAPI) sessions, effectively unifying authentication across SOAP and REST vCenter endpoints.
It can be configured through the common VPXD property ""config.vmacore.soap.maxSessionCount" in the "/etc/vmware-vpx/vpxd.conf" and is also available through the vSphere UI.
**The default maximum number of inflight sessions is now common for both the SOAP and VAPI sessions (as they are one thing) and is 3000.
<config> ... <vmacore> ... <soap> ... <maxSessionCount>6000</maxSessionCount> ... </soap> ... </vmacore> ... </config>
vCenter cloud account datacollection fails in Aria Automation with "The connection with vAPI endpoint can not be established failedToLoginMaxUserSessionCountReached"
https://knowledge.broadcom.com/external/article/312158/vcenter-cloud-account-datacollection-fai.html
Unified Management and Automation Session
Endpoint Limits for Concurrent REST Requests from vCenter APIs - VROOM! Performance Blog