How many API calls does OutboundSync use?
Last updated August 12, 2025
Some customers ask about OutboundSync's API utilization to better understand any potential impact on their Salesforce billing.
Summary
2-4 requests per webhook payload that OutboundSync receives. The number of payloads that OutboundSync receives will vary depending on how your Sales Engagement Platform is configured.
Detailed explanation
The following is an explanation of the specific API calls and context:
- For one payload we are using at a minimum 2 Requests. (Find by email or find by object lookup id and create Email Object or create Task).
- If we should update Contact or Lead we are using +1 Request. If Contact is not found then we are using +1 Request to find Company by domain. Create Contact and Create Company or Create Contact and attach Company is +1 Request.
- We can reduce this by ensuring that the contacts are all in Salesforce first, so every time we look up a Contact or Lead, it's already in there and we're just appending the activities.
An example using email
If you send 100 emails, that's 200-400 API calls to cover the Email Sent events.
Then, we'll have webhook payloads for replies and lead category updates, let's say 10% reply rate (+10 webhook payloads) and all 10 get categorized (+10), so that would be (20x2 + 20x2), that's an additional 80 API calls.
If you're tracking opens, link clicks, bounces, and unsubscribes that can drive an incremental set of API calls. Let's add those up for a total of 120 API calls.
If you want to keep it simple and round up, you could assume approximately 600 API calls for every 100 emails sent, or 6 API calls for every sent email on average.