Conversation Data API Rate Limits
This guide provides detailed information regarding the rate limits for the Conversation Data API and explains how the “Execution User” model impacts your organization’s throughput.
Rate limits are enforced to ensure platform stability and are calculated per Execution User per hour. The following table details the rate limits for each of the Conversation Data APIs:
| API Operation | Endpoint | Rate Limit |
|---|---|---|
| Fetch Entries | GET /conversation-entries | 90 requests per user / minute |
| Delete Participant | DELETE /conversation-participants | 10 requests per user / hour |
| Delete Conversation | DELETE /conversations | 10 requests per user / hour |
Note: There are plans to increase these rate limits in future releases. Until then, if your organization requires higher throughput, please refer to the Scaling API Throughput section below.
When configuring your External Client App to interact with this API, you must select an Execution User. This process is detailed in the Get Started with Conversation Data API guide. This identity serves as the security context that Salesforce uses to run the API flow and return access tokens.
To allow Salesforce to return access tokens, you must select an execution user for the flow. This user must have the API Only User permission enabled in their profile. It is recommended to create a user specifically for this integration rather than using an existing administrative or employee account. During setup, you will set the Run As field to select the user that you want to assign to the client credentials flow.
Because the hourly limits are tied directly to the Execution User assigned to the credentials, the limit is governed by the specific identity rather than a hard cap on the entire organization.
If your business requirements exceed the standard 90 GET requests per minute or 10 DELETE requests per hour, you can scale your total capacity by creating additional execution users. By provisioning a second user in Salesforce with the required “API Only” permissions and configuring a separate External Client App assigned to that user, you generate a separate set of credentials.
Using multiple sets of credentials allows you to distribute your API traffic across different identities. Each Execution User receives their own independent bucket of requests per hour, effectively multiplying your total organizational capacity based on the number of users you configure.