You are here:
Omnichannel API Limits
To maintain optimum performance and ensure that the Force.com API is available to all customers, Salesforce imposes two types of API limits: concurrent API request limits and total API request limits. When a call exceeds a request limit, an error is returned. The actual limit depends on the type of Salesforce edition org you are using, the number of user licenses you have purchased, and the number of additional API calls you may have purchased.
Total API request limits govern the total API requests (or calls) per 24-hour period for an org. Vlocity Omnichannel Web APIs are designed to provide more functionality and data with each request to minimize the number of calls required per user per hour. However, the client application determines the number of API calls.
Concurrent API request limits govern the number of concurrent inbound requests (or calls) with a duration of 20 seconds or longer. Vlocity Omnichannel Web APIs are designed to complete calls much faster than 20 seconds, with the possible exception of a POST of bulk data to Salesforce using an Omnistudio Data Mapper API. Therefore, this limit does not usually apply.
For more information about API limits, see API Limits in the Salesforce Developer Limits Quick Reference.
Other limits apply. Vlocity Omnichannel Web APIs are based on Apex REST. Calls to these APIs count against the deploying company’s API governor limits. All standard Apex governor limits apply to Apex REST classes. For example, the maximum request or response size is 6 MB for synchronous Apex or 12 MB for asynchronous Apex. For more information, see Execution Governors and Limits in the Force.com Apex Code Developer Guide.
