Salesforce API Usage
An overview of Champify’s API usage requirements
Champify has been built from the ground up to be efficient and seamlessly integrated with the Salesforce platform. This means that all resource-intensive operations in Apex have been written as batch jobs that use as few API calls for new record as possible, while still retaining our best-in-class account matching and contact matching behavior when creating or updating records.
Even though Champify is resource efficient, there are situations where even a small number of additional API usage can cause problems. As a result, we have implemented a usage threshold setting that will stop Champify jobs from running as soon as usage passes a specific threshold. For more details, see below.
API Limits and Usage
Since Champify runs as a managed package, and not as a connected app that communicates with Salesforce via OAuth, Champify’s integration with Salesforce is handled by Apex and SOQL. When Champify creates new records activity will count toward your Salesforce organization’s overall usage limits.
By default, to avoid causing resource issues when your organization is already close to reaching its API limits, Champify will stop running jobs when your organization’s total Salesforce API request usage surpasses 95%.
If your organization is frequently hitting this threshold, you can reduce Champify’s impact by updating the “Usage Threshold” value in our custom settings to a number that’s not much higher than your current utilization (such as 85%), and adjust as needed.
Champify will stop running scheduled batch apex jobs when usage surpasses the configured usage threshold for any of the following categories:
- Daily Async Apex Executions
- Daily Bulk API Batches
- Daily API Requests
- Hourly Async Report Runs
- Data Storage MB
For more details about per-organization limits, see Salesforce’s Execution Governors and Limits documentation